deleteSlideElement
Delete an element (image, text box, shape) from a Google Slides slide
This record as markdown: /tools/ark7-google-drive-mcp/deleteslideelement.md
What deleteSlideElement does on Google Drive
AI agents call deleteSlideElement to permanently remove resources in Google Drive, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
objectId | string | Yes | Element object ID to delete |
presentationId | string | Yes | Presentation ID |
Parameters from the server's own tool schema.
Why deleteSlideElement is rated Critical
The tool permanently removes content from a presentation slide. While not as critical as deleting an entire file, this action destroys user data and cannot be reversed through the tool interface itself. An AI agent could inadvertently delete important slide content if given insufficient context or misdirected instructions.
From the tool's definition Tool name explicitly contains 'delete' and description states it removes elements ('Delete an element (image, text box, shape) from a Google Slides slide'). This is an irreversible operation that cannot be undone programmatically through MCP.
Attacks that exploit this kind of access
The rule that runs deleteSlideElement safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteSlideElement, this is the rule to start with:
deleteSlideElement 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 Google Drive, apply this rule, and every deleteSlideElement call is checked against it from then on.
Questions about deleteSlideElement
Delete an element (image, text box, shape) from a Google Slides slide. It is categorised as a Destructive tool in the Google Drive MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deleteSlideElement accepts 3 parameters: account, objectId, presentationId. Required: objectId, presentationId. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for deleteSlideElement: 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 Drive. Nothing to install.
deleteSlideElement 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 deleteSlideElement 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 deleteSlideElement. 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.
deleteSlideElement is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
Across the catalogue