Concepts
The core ideas behind SecureAuth Agent Authority, and how each one shapes what happens on a tool call.
These pages define the terms the rest of the documentation uses. Together they describe how your agents reach your services through the gateway, and what decides, redacts, and records each call along the way. Start with How it works for the model behind all of it, or go straight to the term you need in the glossary.
How it works
Your agents reach your services through one gateway that authenticates, authorizes, and audits each MCP tool call
Agent Registry
Tell an agent apart from its connected instances, and see which tools each agent can call under your policies
Resources
Add catalog and custom MCP servers to your gateway
Access Policies
Define security policies that control which tools agents can use
Data Protection
Redact sensitive data from tool responses before it reaches an agent
Rate limits
Cap how fast agents can call tools, org-wide or split further by user, agent, or tool
Tool search
Give agents a tool to search for tools, so they stop reading every tool definition on every request
Model Providers
Register the model provider endpoints and API keys your organization uses
Tags
Organize agents, MCPs, and tools with labels you can match in policies
Connections
Agents call each service with the requesting user's own access token, never a shared account
Credential modes
Choose whose OAuth app the gateway uses when you install a catalog resource, and who controls it
Authority Graph
See which agents reach which MCP servers through which policy, and which paths went unused in the last 7 days
Human identities
Start an investigation from a person, with their agents, tool calls, spend, and reach on one page
Roles
The three built-in roles, custom roles, and how assigning one widens what a person can do
User portal
Give your users a place to connect their own agents and see only their own activity
Glossary
Short definitions of the terms Agent Authority uses, such as tenant, workspace, policy, tag, and gateway endpoint
Next steps
- How it works – the request-flow model behind every concept here.
- Get started – put these concepts into practice in about 30 minutes.