delete_slide_element
A destructive tool on the Mcp Google Docs MCP server.
This record as markdown: /tools/dev-ithitchhiker-mcp-google-docs/delete-slide-element.md
What delete_slide_element does on Mcp Google Docs
AI agents call delete_slide_element 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.
Why delete_slide_element is rated Critical
The 'delete' operation in the name indicates this tool removes slide elements from a presentation irreversibly. This cannot be undone programmatically by the tool itself, making it Destructive rather than Write. While the blast radius is narrower than deleting entire files, deletion of slide content elements constitutes irreversible data loss.
From the tool's definition Tool name 'delete_slide_element' contains 'delete', indicating removal of data. The server manipulates Google Drive and presentation documents. No description provided, but the operation name explicitly signals irreversible deletion.
Attacks that exploit this kind of access
The rule that runs delete_slide_element safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Docs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_slide_element, this is the rule to start with:
delete_slide_element is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Google Docs, apply this rule, and every delete_slide_element call is checked against it from then on.
Questions about delete_slide_element
delete_slide_element is a destructive tool on the Mcp Google Docs MCP server. 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.
Register the Mcp Google Docs MCP server in PolicyLayer and add a rule for delete_slide_element: 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.
delete_slide_element 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_slide_element 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_slide_element. 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_slide_element is provided by the Mcp Google Docs MCP server (dev-ithitchhiker/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.
Across the catalogue