AI agents call awx_inventory_delete to permanently remove resources in Pypi:awx — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes inventory configurations from an AWX system, which cannot be undone. Inventory in Ansible Tower is a critical configuration asset that defines hosts and groups. Deletion is irreversible and could disrupt automation operations if misused by an agent. This clearly falls under the Destructive category (irreversibly deletes data) rather than Write (which is reversible).
From the tool's definition Tool name is 'awx_inventory_delete' with description 'Delete AWX inventory'. The verb 'delete' and the explicit deletion operation indicate irreversible removal of inventory data from AWX (Ansible Tower).
Documented attack patterns abuse exactly the kind of access awx_inventory_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pypi:awx, and nothing reaches the server without passing your rules. This is the rule we recommend for awx_inventory_delete:
{
"version": "1",
"default": "deny",
"hide": [
"awx_inventory_delete"
]
} awx_inventory_delete 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 AWX inventory. It is categorised as a Destructive tool in the Pypi:awx MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pypi:awx MCP server in PolicyLayer and add a rule for awx_inventory_delete: 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 Pypi:awx. Nothing to install.
awx_inventory_delete 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 awx_inventory_delete 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 awx_inventory_delete. 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.
awx_inventory_delete is provided by the Pypi:awx MCP server (SurgeX-Labs/awx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pypi:awx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
50 Pypi:awx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.