This record as markdown: /tools/secure-ssid-centralmcp/delete-aaa-profile.md
What delete_aaa_profile does on API-Central
AI agents call delete_aaa_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.
Why delete_aaa_profile is rated Critical
Deletion of AAA profiles is an irreversible action that cannot be undone and removes critical authentication infrastructure configuration. This constitutes a destructive operation with high severity due to the potential impact on network access control and security posture.
From the tool's definition Tool name 'delete_aaa_profile' explicitly performs deletion of an AAA (authentication, authorization, accounting) profile by name. The verb 'delete' indicates irreversible removal of configuration data.
Attacks that exploit this kind of access
The rule that runs delete_aaa_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_aaa_profile, this is the rule to start with:
delete_aaa_profile is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every delete_aaa_profile call is checked against it from then on.
Questions about delete_aaa_profile
Delete an AAA 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_aaa_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_aaa_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_aaa_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_aaa_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_aaa_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.
More on API-Central, and thousands of servers like it.
Across the catalogue