Delete a Central NAC authentication profile by UUID.
AI agents call delete_auth_profile 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 deletes authentication profiles, which cannot be undone. Deletion of security-related configurations like NAC authentication profiles is a destructive action with significant blast radius—an agent could remove authentication mechanisms that protect network access, disrupting security posture and potentially requiring manual recovery or reconfiguration.
From the tool's definition Tool name contains 'delete' and description states 'Delete a Central NAC authentication profile by UUID.' The action is irreversible and removes security infrastructure configuration.
Attacks that exploit this kind of access
Delete a Central NAC authentication profile by UUID. 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_profile: 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_profile 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_profile 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_profile. 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_profile 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 →