delete_range
AI agents call delete_range to permanently remove resources in Google Docs MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete_range' operation deletes data from Google Docs without reversibility. This is categorized as Destructive rather than Write because deletion cannot be undone by the tool itself (undo is a client-side feature, not part of the API contract). High severity because an agent misusing this could irreversibly remove critical document sections.
From the tool's definition Tool named 'delete_range' with empty description. The name explicitly indicates deletion of content range from a document. In context of a Google Docs MCP server that handles document editing, this tool irreversibly removes content.
Attacks that exploit this kind of access
delete_range. It is categorised as a Destructive tool in the Google Docs MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Docs MCP Server MCP server in PolicyLayer and add a rule for delete_range: 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 MCP Server. Nothing to install.
delete_range 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 delete_range 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 delete_range. 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.
delete_range is provided by the Google Docs MCP Server MCP server (nickweedon/google-docs-mcp-docker). 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 →