delete_object
Deletes a slide or a page element (shape, image, table, video, line, group) by object id — batchUpdate deleteObject. Deleting a slide removes all its elements and speaker notes; deleting a group removes its children. There is no undo through the API (version history lives in the Slides UI). It ca...
This record as markdown: /tools/a1-x-tech-mcp-google-slides/delete-object.md
What delete_object does on Mcp Google Slides
AI agents call delete_object to permanently remove resources in Mcp Google Slides, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
object_id | string | Yes | The object id of the slide or page element to delete (from list_slides). |
presentation_id | string | Yes | The presentation id — the long id from the URL (docs.google.com/presentation/d/<presentationId>/edit) or from create_presentation output. |
Parameters from the server's own tool schema.
Why delete_object is rated Critical
Irreversibly removes presentation content without undo capability via API.
From the tool's definition Deletes slide or page element; no undo through API
Attacks that exploit this kind of access
The rule that runs delete_object safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Slides, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_object, this is the rule to start with:
delete_object 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 Slides, apply this rule, and every delete_object call is checked against it from then on.
Questions about delete_object
Deletes a slide or a page element (shape, image, table, video, line, group) by object id — batchUpdate deleteObject. Deleting a slide removes all its elements and speaker notes; deleting a group removes its children. There is no undo through the API (version history lives in the Slides UI). It cannot delete the whole presentation — that is a Drive file operation outside this server. It is categorised as a Destructive tool in the Mcp Google Slides MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_object accepts 2 parameters: object_id, presentation_id. Required: object_id, presentation_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Google Slides MCP server in PolicyLayer and add a rule for delete_object: 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 Slides. Nothing to install.
delete_object 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_object 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_object. 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_object is provided by the Mcp Google Slides MCP server (@a1-x-tech/mcp-google-slides). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Slides, and thousands of servers like it.
Across the catalogue