deleteTodo

THE RISK

Critical Risk

Why deleteTodo needs a policy

Deletion operations are destructive because they cannot be undone and permanently remove data. While the blast radius is limited to todo items (not critical system data), the action is irreversible, placing it in the Destructive category with high severity.

From the tool's definition Tool name is 'deleteTodo' and description states 'Delete a todo' — this irreversibly removes data.

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

POLICY

How to control deleteTodo

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

policy.json

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

deleteTodo 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 TypeSpec MCP Server — 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 TypeSpec MCP Server tools

Destructive gists_delete Delete a gist Execute build Build typespec mcp project Execute compile Compile the typespec project in the given directory. Execute call_endpoint Call the given endpoint.\nUse the Execute math_dot_product Computes the dot product of two vectors. Use this to find the scalar\nprojection of one ve Execute math_sub_vector Subtracts one vector from another. Use this to find the difference between\ntwo vectors. F Execute math_add_vector Adds two vectors together. Use this when you want to combine two vectors to\nget a resulta Write gists_fork Fork a gist

All 28 TypeSpec MCP Server 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 TypeSpec MCP Server → 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 deleteTodo

What does the deleteTodo tool do? +

Delete a todo. It is categorised as a Destructive tool in the TypeSpec 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 deleteTodo? +

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

What risk level is deleteTodo? +

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

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

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

deleteTodo is provided by the TypeSpec MCP Server MCP server (microsoft/typespec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TypeSpec MCP Server tool call.

Start from TypeSpec MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →