This record as markdown: /tools/ark7-google-drive-mcp/duplicateslide.md
What duplicateSlide does on Google Drive
AI agents use duplicateSlide 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 |
|---|---|---|---|
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 |
slideObjectId | string | Yes | Slide object ID |
presentationId | string | Yes | Presentation ID |
Parameters from the server's own tool schema.
Why duplicateSlide is rated Medium
This tool creates a new slide by copying an existing one, which is a reversible write operation. The duplicate can be deleted, and the original remains unchanged. There is no data destruction, no code execution, no financial impact, and no external system manipulation. The blast radius is minimal—an agent misusing this tool could create unwanted slide copies, but these can be easily undone.
From the tool's definition duplicateSlide duplicates a slide in a presentation, creating a new copy of existing content
Attacks that exploit this kind of access
The rule that runs duplicateSlide 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 duplicateSlide, this is the rule to start with:
duplicateSlide 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 duplicateSlide call is checked against it from then on.
Questions about duplicateSlide
Duplicate a slide in a 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.
duplicateSlide accepts 3 parameters: account, slideObjectId, presentationId. Required: slideObjectId, 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 duplicateSlide: 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.
duplicateSlide 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 duplicateSlide 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 duplicateSlide. 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.
duplicateSlide 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