Delete a named range from a Google Doc by name or ID.
AI agents call delete_named_range to permanently remove resources in Google — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Named ranges are structural metadata in Google Sheets/Docs that organize and reference cell groups. Deletion cannot be undone by the tool itself and requires recovery from version history or backups. This is a destructive operation affecting document organization. Severity is high rather than critical because the scope is limited to named range metadata rather than bulk data deletion, but it is clearly irreversible.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a named range from a Google Doc' — irreversible removal of a spreadsheet/document structure element.
Attacks that exploit this kind of access
Delete a named range from a Google Doc by name or ID. It is categorised as a Destructive tool in the Google MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google MCP server in PolicyLayer and add a rule for delete_named_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. Nothing to install.
delete_named_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_named_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_named_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_named_range is provided by the Google MCP server (ztgluis/google-mcp). 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 →