Update an existing Google Slides presentation
AI agents use updateGoogleSlides to create or update resources in Google Drive MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive MCP Server environment.
Updating a presentation is a Write operation: it creates or modifies data reversibly without irreversible deletion or executing arbitrary code. However, severity is high because unauthorized modifications to shared presentations could disrupt collaboration, alter important information, and impact multiple stakeholders who rely on the document's accuracy.
From the tool's definition Tool name and description: 'Update an existing Google Slides presentation' — this modifies document content reversibly. The sibling tools (addComment, addSheet, appendSpreadsheetRows) confirm this server's write-capable nature.
Documented attack patterns abuse exactly the kind of access updateGoogleSlides gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Drive MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for updateGoogleSlides:
{
"version": "1",
"default": "deny",
"tools": {
"updateGoogleSlides": {
"limits": [
{
"counter": "updategoogleslides_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}updateGoogleSlides stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update an existing Google Slides presentation. It is categorised as a Write tool in the Google Drive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Drive MCP Server MCP server in PolicyLayer and add a rule for updateGoogleSlides: 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 MCP Server. Nothing to install.
updateGoogleSlides is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the updateGoogleSlides 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 updateGoogleSlides. 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.
updateGoogleSlides is provided by the Google Drive MCP Server MCP server (piotr-agier/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 107 Google Drive MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
107 Google Drive MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.