Critical Risk →

delete_execution_plan

Delete an execution plan by ID

How to control delete_execution_plan ↓

AI agents call delete_execution_plan to permanently remove resources in ZMCPTools — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool permanently removes execution plans from the system. In a multi-agent orchestration platform, execution plans likely represent complex task workflows and coordination state. Deletion cannot be undone and would disrupt agent coordination, making it a destructive operation.

From the tool's definition Tool name is 'delete_execution_plan' with description 'Delete an execution plan by ID'. The verb 'delete' is explicitly destructive and irreversible.

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

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

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

delete_execution_plan 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 ZMCPTools — 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_execution_plan tool do? +

Delete an execution plan by ID. It is categorised as a Destructive tool in the ZMCPTools 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_execution_plan? +

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

What risk level is delete_execution_plan? +

delete_execution_plan 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_execution_plan? +

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

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

delete_execution_plan is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ZMCPTools tool call.

Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

70 ZMCPTools 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.