reorderSlides
Reorder one or more slides in a presentation
This record as markdown: /tools/ark7-google-drive-mcp/reorderslides.md
What reorderSlides does on Google Drive
AI agents use reorderSlides 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 |
insertionIndex | number | Yes | Target insertion index |
presentationId | string | Yes | Presentation ID |
slideObjectIds | array | Yes | Slide object IDs to move |
Parameters from the server's own tool schema.
Why reorderSlides is rated Medium
Reordering slides modifies a document's content organization but is fully reversible—slides can be reordered again to restore original order. It does not delete data (Destructive), execute code (Execute), create financial obligations (Financial), or merely read data (Read). This is a clear Write operation.
From the tool's definition Tool name 'reorderSlides' and description 'Reorder one or more slides in a presentation' indicate modification of presentation structure. This is a reversible operation that modifies existing data without deletion or external execution.
Attacks that exploit this kind of access
The rule that runs reorderSlides 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 reorderSlides, this is the rule to start with:
reorderSlides 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 reorderSlides call is checked against it from then on.
Questions about reorderSlides
Reorder one or more slides 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.
reorderSlides accepts 4 parameters: account, insertionIndex, presentationId, slideObjectIds. Required: insertionIndex, presentationId, slideObjectIds. 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 reorderSlides: 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.
reorderSlides 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 reorderSlides 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 reorderSlides. 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.
reorderSlides 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