move_slides
Moves one or more slides to a new position (batchUpdate updateSlidesPosition). slide_object_ids must appear in their current deck order with no duplicates; insertion_index is the 0-based position BEFORE the move is applied (moving a slide down: index counts with the slide still in its old place)....
This record as markdown: /tools/a1-x-tech-mcp-google-slides/move-slides.md
What move_slides does on Mcp Google Slides
AI agents use move_slides 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 |
|---|---|---|---|
insertion_index | integer | Yes | 0-based target position, evaluated before the slides are removed from their old places. |
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_ids | array | Yes | The slides to move, listed in their current presentation order. |
Parameters from the server's own tool schema.
Why move_slides is rated Medium
Reorders slides within a presentation without deleting or destroying content; changes are reversible.
From the tool's definition Moves one or more slides to a new position; batchUpdate; reversible modification
Attacks that exploit this kind of access
The rule that runs move_slides 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 move_slides, this is the rule to start with:
move_slides 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 move_slides call is checked against it from then on.
Questions about move_slides
Moves one or more slides to a new position (batchUpdate updateSlidesPosition). slide_object_ids must appear in their current deck order with no duplicates; insertion_index is the 0-based position BEFORE the move is applied (moving a slide down: index counts with the slide still in its old place). Use list_slides to see the current order first. 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.
move_slides accepts 3 parameters: insertion_index, presentation_id, slide_object_ids. Required: insertion_index, presentation_id, slide_object_ids. 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 move_slides: 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.
move_slides 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 move_slides 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 move_slides. 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.
move_slides 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