Delete an AAP user. DESTRUCTIVE - requires confirmation.
AI agents call aap_delete_user to permanently remove resources in AAP MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a user account from the Ansible Automation Platform. User deletion is an irreversible action that destroys account data and access credentials. While the description notes it 'requires confirmation', confirmation is a mitigation control rather than a category change. The deletion operation itself cannot be reversed, fitting the Destructive category definition.
From the tool's definition Tool name is 'aap_delete_user' and description explicitly states 'Delete an AAP user' with 'DESTRUCTIVE' label. Deletion of user accounts is irreversible and cannot be undone.
Attacks that exploit this kind of access
Delete an AAP user. DESTRUCTIVE - requires confirmation. It is categorised as a Destructive tool in the AAP MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AAP MCP Server MCP server in PolicyLayer and add a rule for aap_delete_user: 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 AAP MCP Server. Nothing to install.
aap_delete_user 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 aap_delete_user 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 aap_delete_user. 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.
aap_delete_user is provided by the AAP MCP Server MCP server (srinivassrinu842/aap-mcp-server). 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 →