update_transform
Moves and/or scales a page element (batchUpdate updatePageElementTransform). mode=absolute REPLACES the element's whole transform: translate_x_pt/translate_y_pt become the new top-left-ish origin and omitted scales default to 1 — NOT to the current values, so an absolute move of a scaled element ...
This record as markdown: /tools/a1-x-tech-mcp-google-slides/update-transform.md
What update_transform does on Mcp Google Slides
AI agents use update_transform 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 |
|---|---|---|---|
mode | string | Yes | absolute = replace the whole transform; relative = multiply onto the current one. |
scale_x | number | — | Horizontal scale factor (default 1). |
scale_y | number | — | Vertical scale factor (default 1). |
object_id | string | Yes | The page element's object id (from list_slides). |
translate_x_pt | number | — | Horizontal translation in points (default 0). |
translate_y_pt | number | — | Vertical translation in points (default 0). |
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. |
Parameters from the server's own tool schema.
Why update_transform is rated Medium
Modifies presentation element properties reversibly without permanent deletion or external code execution.
From the tool's definition Moves and/or scales a page element; updates transform, translate, scale properties.
Attacks that exploit this kind of access
The rule that runs update_transform 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 update_transform, this is the rule to start with:
update_transform 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 update_transform call is checked against it from then on.
Questions about update_transform
Moves and/or scales a page element (batchUpdate updatePageElementTransform). mode=absolute REPLACES the element's whole transform: translate_x_pt/translate_y_pt become the new top-left-ish origin and omitted scales default to 1 — NOT to the current values, so an absolute move of a scaled element also resets its scale unless you resend it. mode=relative multiplies onto the existing transform: translate shifts by the given points, scale 2 doubles the current size (scaling happens around the origin, which also shifts the element — for a simple move prefer relative translate only). Element geometry to reason from is in get_page. 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.
update_transform accepts 7 parameters: mode, scale_x, scale_y, object_id, translate_x_pt, translate_y_pt, presentation_id. Required: mode, object_id, presentation_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 update_transform: 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.
update_transform 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 update_transform 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 update_transform. 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.
update_transform 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