New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_range

Deletes the content in [start_index, end_index) — text, inline images, whole tables or any mix, as long as the range does not cut across a table cell boundary. Get fresh indexes from read_document_text first; every delete shifts all later indexes down. Deleting a paragraph's trailing newline merg...

SERVERMcp Google Docs SOURCE@a1-x-tech/mcp-google-docs
Critical RISK CLASS
Category Destructive
Parameters 53 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/a1-x-tech-mcp-google-docs/delete-range.md

What delete_range does on Mcp Google Docs

AI agents call delete_range to permanently remove resources in Mcp Google Docs, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
tab_id string — Tab to target (from list_tabs). Omit for the first/only tab.
end_index integer Yes End of the range to delete (exclusive).
segment_id string — Header/footer/footnote segment id (from get_document). Omit for the document body.
document_id string Yes The document id — the long id from the document URL (docs.google.com/document/d/<documentId>/edit) or from create_document output.
start_index integer Yes Start of the range to delete (inclusive).

Parameters from the server's own tool schema.

Why delete_range is rated Critical

An AI agent that decides to call delete_range doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Google Docs is gone. There is no undo for destructive operations.

Risk signalsBulk/mass operation — affects multiple targets

Questions about delete_range

What does the delete_range tool do? +

Deletes the content in [start_index, end_index) — text, inline images, whole tables or any mix, as long as the range does not cut across a table cell boundary. Get fresh indexes from read_document_text first; every delete shifts all later indexes down. Deleting a paragraph's trailing newline merges it with the next paragraph. The tab's final newline cannot be deleted. This is final — there is no undo through the API. It is categorised as a Destructive tool in the Mcp Google Docs MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does delete_range accept? +

delete_range accepts 5 parameters: tab_id, end_index, segment_id, document_id, start_index. Required: end_index, document_id, start_index. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on delete_range? +

Register the Mcp Google Docs 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 Mcp Google Docs. Nothing to install.

What risk level is delete_range? +

delete_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 delete_range? +

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.

How do I block delete_range completely? +

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.

What MCP server provides delete_range? +

delete_range is provided by the Mcp Google Docs MCP server (@a1-x-tech/mcp-google-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Mcp Google Docs, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Google Docs's. Pull the full record:

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.