Critical Risk →

awx_job_delete

Delete/remove an AWX job record from history. Use this when user asks to

How to control awx_job_delete ↓

What awx_job_delete does on Pypi:awx

AI agents call awx_job_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.

Critical Risk

Why awx_job_delete needs a policy

This tool irreversibly deletes job execution records from AWX (Ansible Tower). Deletion of historical job records cannot be undone and represents a destructive action with potential operational impact (loss of audit trails, execution history, and operational visibility). This is the most severe category applicable.

From the tool's definition Tool name 'awx_job_delete' and description explicitly states 'Delete/remove an AWX job record from history.' The use of 'delete' and 'remove' combined with 'irreversibly' deletes historical job records.

Documented attack patterns abuse exactly the kind of access awx_job_delete gives an agent:

How to control awx_job_delete

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_job_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "awx_job_delete"
  ]
}

awx_job_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Pypi:awx — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about awx_job_delete

What does the awx_job_delete tool do? +

Delete/remove an AWX job record from history. Use this when user asks to. 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.

How do I enforce a policy on awx_job_delete? +

Register the Pypi:awx MCP server in PolicyLayer and add a rule for awx_job_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.

What risk level is awx_job_delete? +

awx_job_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit awx_job_delete? +

Yes. Add a rate_limit block to the awx_job_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.

How do I block awx_job_delete completely? +

Set action: deny in the PolicyLayer policy for awx_job_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.

What MCP server provides awx_job_delete? +

awx_job_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.

Enforce policy on every Pypi:awx tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.