Critical Risk →

delete_host

Delete a host from inventory.

How to control delete_host ↓

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

Critical Risk

Deleting a host from inventory cannot be undone without manual restoration or backups. This permanently removes infrastructure metadata from Ansible's automation scope. In a multi-tenant or production environment, accidental deletion could cause significant operational disruption, failed deployments, or loss of infrastructure tracking.

From the tool's definition Tool name is 'delete_host' and description states 'Delete a host from inventory.' The verb 'delete' combined with the irreversible removal of a host record indicates a destructive operation.

Documented attack patterns abuse exactly the kind of access delete_host 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_host:

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

delete_host 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 AAP Enterprise MCP Server — 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.

Go deeper

What does the delete_host tool do? +

Delete a host from inventory. 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.

How do I enforce a policy on delete_host? +

Register the AAP Enterprise MCP Server MCP server in PolicyLayer and add a rule for delete_host: 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.

What risk level is delete_host? +

delete_host 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 delete_host? +

Yes. Add a rate_limit block to the delete_host 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 delete_host completely? +

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

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

Enforce policy on every AAP Enterprise MCP Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.