Critical Risk →

google_slides_delete_slide

Delete a slide from a presentation by its object ID

How to control google_slides_delete_slide ↓

AI agents call google_slides_delete_slide to permanently remove resources in Sage MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool performs an irreversible deletion operation on presentation content. Once a slide is deleted from a Google Slides presentation, it cannot be automatically recovered through the tool's normal operation. This is a classic destructive action that cannot be undone by the tool itself, placing it in the Destructive category rather than Write.

From the tool's definition Tool name is 'google_slides_delete_slide' and description states 'Delete a slide from a presentation by its object ID'. The verb 'delete' combined with the action of removing a slide indicates irreversible data destruction.

Documented attack patterns abuse exactly the kind of access google_slides_delete_slide gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for google_slides_delete_slide:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "google_slides_delete_slide"
  ]
}

google_slides_delete_slide disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the google_slides_delete_slide tool do? +

Delete a slide from a presentation by its object ID. It is categorised as a Destructive tool in the Sage MCP 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 google_slides_delete_slide? +

Register the Sage MCP server in PolicyLayer and add a rule for google_slides_delete_slide: 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 Sage MCP. Nothing to install.

What risk level is google_slides_delete_slide? +

google_slides_delete_slide 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 google_slides_delete_slide? +

Yes. Add a rate_limit block to the google_slides_delete_slide 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 google_slides_delete_slide completely? +

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

google_slides_delete_slide is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sage MCP tool call.

Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.