gdoc_delete_named_range

Delete a named range by ID or name. Does not delete the content, only the reference.

Server Google Docs node2flow-th/google-docs-mcp-community
Category Destructive
Risk class Critical
Parameters 00 required

What gdoc_delete_named_range does on Google Docs

AI agents call gdoc_delete_named_range 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.

Why gdoc_delete_named_range needs a policy

Named ranges in Google Docs are document structural metadata that users rely upon for document organization, navigation, and programmatic reference. Deletion of a named range is irreversible—once deleted, any macros, scripts, or document workflows depending on that reference will break. While the content itself is preserved, the semantic structure and all references pointing to that range are destroyed.

From the tool's definition Tool name contains 'delete' and description states 'Delete a named range by ID or name.' The action irreversibly removes a named range reference, which cannot be undone through normal means.

Questions about gdoc_delete_named_range

What does the gdoc_delete_named_range tool do? +

Delete a named range by ID or name. Does not delete the content, only the reference. 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.

How do I enforce a policy on gdoc_delete_named_range? +

Register the Google Docs MCP server in PolicyLayer and add a rule for gdoc_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 Docs. Nothing to install.

What risk level is gdoc_delete_named_range? +

gdoc_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.

Can I rate-limit gdoc_delete_named_range? +

Yes. Add a rate_limit block to the gdoc_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.

How do I block gdoc_delete_named_range completely? +

Set action: deny in the PolicyLayer policy for gdoc_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.

What MCP server provides gdoc_delete_named_range? +

gdoc_delete_named_range 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.