Delete a RADIUS/auth server profile by name.
AI agents call delete_auth_server to permanently remove resources in API-Central — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes authentication infrastructure configurations. Deletion of RADIUS/auth server profiles cannot be easily undone and would disrupt authentication services for network users if misapplied. This represents an irreversible data destruction action matching the Destructive category definition.
From the tool's definition Tool name contains 'delete' and description states 'Delete a RADIUS/auth server profile by name.' The verb 'delete' combined with the irreversible removal of an authentication server configuration indicates a destructive operation.
Attacks that exploit this kind of access
Delete a RADIUS/auth server profile by name. It is categorised as a Destructive tool in the API-Central MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the API-Central MCP server in PolicyLayer and add a rule for delete_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.
delete_auth_server is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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 →