Get a single RADIUS/auth server profile by name.
AI agents call get_auth_server to retrieve information from API-Central without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing authentication server configuration data. It queries and returns information about a RADIUS/auth server profile without creating, modifying, deleting, or executing any operations. This is a straightforward read operation with minimal blast radius - exposure would allow an attacker to view auth server configurations but not alter network security policies or execute commands.
From the tool's definition 'Get a single RADIUS/auth server profile by name' - the verb 'Get' and the operation of retrieving an auth server profile by name indicates data retrieval with no modifications or side effects.
Attacks that exploit this kind of access
Get a single RADIUS/auth server profile by name. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central MCP server in PolicyLayer and add a rule for get_auth_server: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches API-Central. Nothing to install.
get_auth_server is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_auth_server rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_auth_server. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_auth_server is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →