Critical Risk →

deleteAgent

Delete an agent

How to control deleteAgent ↓

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

Critical Risk

Deleting an agent cannot be undone and permanently removes data/configuration. This is a destructive action with potentially high blast radius if triggered accidentally or maliciously, affecting all dependent workflows or access tied to that agent.

From the tool's definition Tool name is 'deleteAgent' and description states 'Delete an agent' — this is an irreversible deletion operation.

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

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

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

deleteAgent 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 Mcp Taskade — 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 deleteAgent tool do? +

Delete an agent. It is categorised as a Destructive tool in the Mcp Taskade 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 deleteAgent? +

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

What risk level is deleteAgent? +

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

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

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

deleteAgent is provided by the Mcp Taskade MCP server (taskade/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Taskade tool call.

Deterministic rules across all 57 Mcp Taskade tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

57 Mcp Taskade 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.