AI agents call delete_activation to permanently remove resources in AAP Enterprise 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 an activation resource from Red Hat's Ansible Automation Platform. Activations are license/subscription entities, and deletion destroys the record irreversibly. This constitutes a destructive action with potentially significant operational impact (loss of automation platform access, licensing issues). The blast radius is high if an AI agent mistakenly deletes critical activations.
From the tool's definition Tool name is 'delete_activation' with description 'Delete an activation.' The verb 'delete' and the action of removing an activation record are irreversible operations that cannot be undone without manual intervention or backups.
Documented attack patterns abuse exactly the kind of access delete_activation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AAP Enterprise MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_activation:
{
"version": "1",
"default": "deny",
"hide": [
"delete_activation"
]
}delete_activation disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an activation. It is categorised as a Destructive tool in the AAP Enterprise MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AAP Enterprise MCP Server MCP server in PolicyLayer and add a rule for delete_activation: 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 Enterprise MCP Server. Nothing to install.
delete_activation 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_activation 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_activation. 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_activation is provided by the AAP Enterprise MCP Server MCP server (sibilleb/aap-enterprise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 69 AAP Enterprise MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
69 AAP Enterprise MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.