delete_tool_policy

THE RISK

Critical Risk

Why delete_tool_policy needs a policy

This tool permanently deletes enforcement policy configurations. While not data destruction in the traditional sense, removal of a governance policy is irreversible and weakens security controls for an AI agent—a governance system's core function. An agent that deletes policies could remove critical compliance constraints, making this a destructive action with high blast radius.

From the tool's definition Tool name is 'delete_tool_policy' with description 'Remove a local enforcement policy for a tool.' The use of 'Remove' and 'delete' indicates irreversible deletion of a policy configuration.

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

POLICY

How to control delete_tool_policy

PolicyLayer is an MCP gateway — it sits between your AI agents and Pypi:asqav, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_tool_policy:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_tool_policy"
  ]
}

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

Create a free account and register Pypi:asqav — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Pypi:asqav tools

Execute enforced_tool_call enforced_tool_call Execute gate_action gate_action Write create_tool_policy create_tool_policy Read check_policy Check if an action is allowed by the organization's policies. Read get_agent Get details for a specific AI agent. Read list_agents List all registered AI agents in the organization. Read list_tool_policies List all active local tool enforcement policies. Read preflight_check Combined agent-status + policy-allowed check; returns CLEARED / NOT CLEARED summary.

All 15 Pypi:asqav tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Pypi:asqav → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_tool_policy

What does the delete_tool_policy tool do? +

Remove a local enforcement policy for a tool. It is categorised as a Destructive tool in the Pypi:asqav 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_tool_policy? +

Register the Pypi:asqav MCP server in PolicyLayer and add a rule for delete_tool_policy: 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:asqav. Nothing to install.

What risk level is delete_tool_policy? +

delete_tool_policy 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_tool_policy? +

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

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

delete_tool_policy is provided by the Pypi:asqav MCP server (jagmarques/asqav-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pypi:asqav tool call.

Start from Pypi:asqav, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →