Delete content in a range. Get indices from gdoc_get response.
AI agents call gdoc_delete_content to permanently remove resources in Google Docs — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool deletes content from Google Docs documents, which is an irreversible operation that cannot be undone programmatically. Once content is deleted via this API call, it is gone unless manually restored from revision history. This qualifies as Destructive rather than Write because deletion is not a reversible modification — it permanently removes data.
From the tool's definition Tool name is 'gdoc_delete_content' and description states 'Delete content in a range' — explicitly performs irreversible deletion of document content.
Attacks that exploit this kind of access
Delete content in a range. Get indices from gdoc_get response. It is categorised as a Destructive tool in the Google Docs MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Docs MCP server in PolicyLayer and add a rule for gdoc_delete_content: 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 Google Docs. Nothing to install.
gdoc_delete_content 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 gdoc_delete_content 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 gdoc_delete_content. 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.
gdoc_delete_content is provided by the Google Docs MCP server (node2flow-th/google-docs-mcp-community). 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 →