updateGoogleSlides
Update an existing Google Slides presentation
This record as markdown: /tools/ark7-google-drive-mcp/updategoogleslides.md
What updateGoogleSlides does on Google Drive
AI agents use updateGoogleSlides to create or update resources in Google Drive, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
slides | array | Yes | Array of slide objects to replace existing slides |
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 |
presentationId | string | Yes | Presentation ID |
Parameters from the server's own tool schema.
Why updateGoogleSlides is rated Medium
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.
Risk signalsAccepts raw HTML/template content (slides[].content)
Attacks that exploit this kind of access
The rule that runs updateGoogleSlides 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 updateGoogleSlides, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Drive, apply this rule, and every updateGoogleSlides call is checked against it from then on.
Questions about updateGoogleSlides
Update an existing Google Slides presentation. It is categorised as a Write tool in the Google Drive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
updateGoogleSlides accepts 3 parameters: slides, account, presentationId. Required: slides, 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 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. 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 (@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.
This server
Across the catalogue