Delete a header from the document. Get the header ID from gdoc_get.
AI agents call gdoc_delete_header 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 irreversibly deletes document headers, which cannot be undone through the tool itself. While not data loss on the scale of document deletion, header removal is a destructive write that alters document structure permanently. High severity due to potential for accidental removal of important document formatting in multi-user or agent-controlled scenarios.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a header from the document'—an irreversible operation that removes content.
Attacks that exploit this kind of access
Delete a header from the document. Get the header ID from gdoc_get. 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_header: 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_header 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_header 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_header. 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_header 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 →