delete_doc

THE RISK

Critical Risk

Why delete_doc needs a policy

This tool irreversibly deletes entire documents. The description explicitly states the action is permanent and cannot be undone, which is the defining characteristic of the Destructive category. The blast radius is high because a single misuse could eliminate substantial work and data. Confidence is very high given the unambiguous destructive intent.

From the tool's definition "Permanently delete a Coda doc by ID - use with extreme caution as this cannot be undone"

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

POLICY

How to control delete_doc

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

policy.json

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

delete_doc 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 Coda — 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 Coda tools

Destructive delete_page Delete a page from a Coda doc by its ID or name Destructive delete_row Delete a specific row from a table by its ID or name Destructive delete_rows Delete multiple rows from a table at once using a list of row IDs Execute begin_page_content_export begin_page_content_export Write create_doc create_doc Write create_page create_page Write update_doc Update properties of a Coda doc including title and icon Write update_page update_page

All 24 Coda 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 Coda → 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_doc

What does the delete_doc tool do? +

Permanently delete a Coda doc by ID - use with extreme caution as this cannot be undone. It is categorised as a Destructive tool in the Coda 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_doc? +

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

What risk level is delete_doc? +

delete_doc 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_doc? +

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

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

delete_doc is provided by the Coda MCP server (tjc-lp/coda-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 Coda tool call.

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

CHECK YOUR STACK →