moveSlideElement
Move and/or resize an element (image, text box, shape) on a Google Slides slide
This record as markdown: /tools/ark7-google-drive-mcp/moveslideelement.md
What moveSlideElement does on Google Drive
AI agents use moveSlideElement 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 |
|---|---|---|---|
x | number | — | New X position in EMU |
y | number | — | New Y position in EMU |
width | number | — | New width in EMU |
height | number | — | New height in EMU |
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 |
objectId | string | Yes | Element object ID to move/resize |
presentationId | string | Yes | Presentation ID |
Parameters from the server's own tool schema.
Why moveSlideElement is rated Medium
This tool creates or modifies data reversibly by changing element positions and sizes within a slide. It does not delete data (which would be Destructive), execute arbitrary code (which would be Execute), nor retrieve data without modification (which would be Read). The modification is reversible and has a contained blast radius to the specific slide's layout.
From the tool's definition moveSlideElement moves and/or resizes elements on a Google Slides slide. This modifies the presentation content (position and dimensions of objects) but is reversible—the previous state can be restored by moving elements back.
Attacks that exploit this kind of access
The rule that runs moveSlideElement 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 moveSlideElement, this is the rule to start with:
moveSlideElement 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 moveSlideElement call is checked against it from then on.
Questions about moveSlideElement
Move and/or resize an element (image, text box, shape) on a Google Slides slide. 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.
moveSlideElement accepts 7 parameters: x, y, width, height, account, objectId, presentationId. Required: objectId, 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 moveSlideElement: 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.
moveSlideElement 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 moveSlideElement 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 moveSlideElement. 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.
moveSlideElement 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