duplicate_slide
Duplicates a slide (batchUpdate duplicateObject) — the copy, with all its elements and speaker notes, lands immediately after the original and its new objectId comes back in the reply. Works on any page element id too (the copy lands on the same slide, slightly offset). Move the copy with move_sl...
This record as markdown: /tools/a1-x-tech-mcp-google-slides/duplicate-slide.md
What duplicate_slide does on Mcp Google Slides
AI agents use duplicate_slide to create or update resources in Mcp Google Slides, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Slides environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
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. |
slide_object_id | string | Yes | The object id of the slide (or page element) to duplicate. |
Parameters from the server's own tool schema.
Why duplicate_slide is rated Medium
Creates new slide copy reversibly; modifiable and deletable without permanent data loss.
From the tool's definition Duplicates slide, creates copy, new objectId returned
Attacks that exploit this kind of access
The rule that runs duplicate_slide 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 duplicate_slide, this is the rule to start with:
duplicate_slide 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 Mcp Google Slides, apply this rule, and every duplicate_slide call is checked against it from then on.
Questions about duplicate_slide
Duplicates a slide (batchUpdate duplicateObject) — the copy, with all its elements and speaker notes, lands immediately after the original and its new objectId comes back in the reply. Works on any page element id too (the copy lands on the same slide, slightly offset). Move the copy with move_slides afterwards if needed. It is categorised as a Write tool in the Mcp Google Slides MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
duplicate_slide accepts 2 parameters: presentation_id, slide_object_id. Required: presentation_id, slide_object_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 duplicate_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 Mcp Google Slides. Nothing to install.
duplicate_slide 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 duplicate_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.
Set action: deny in the PolicyLayer policy for duplicate_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.
duplicate_slide 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.
This server
Across the catalogue