Delete a Coda document permanently. THIS ACTION IS IRREVERSIBLE. Args: - doc_id (string): The document ID to delete Returns: Confirmation of deletion.
AI agents call coda_delete_doc to permanently remove resources in Coda MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly states it permanently and irreversibly deletes an entire Coda document. This is the highest-impact destructive action possible — wiping all pages, tables, and data within a document with no undo path.
From the tool's definition "Delete a Coda document permanently. THIS ACTION IS IRREVERSIBLE."
Attacks that exploit this kind of access
Delete a Coda document permanently. THIS ACTION IS IRREVERSIBLE. Args: - doc_id (string): The document ID to delete Returns: Confirmation of deletion. It is categorised as a Destructive tool in the Coda MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Coda MCP Server MCP server in PolicyLayer and add a rule for coda_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 MCP Server. Nothing to install.
coda_delete_doc is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the coda_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.
Set action: deny in the PolicyLayer policy for coda_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.
coda_delete_doc is provided by the Coda MCP Server MCP server (thierryvm/coda-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →