replaceSlideImage
Replace an existing image in place, preserving its layering (z-order), position, size, and crop. Unlike delete+insert, which lands the new image on top of the stack, this keeps the image under any overlaid text.
This record as markdown: /tools/ark7-google-drive-mcp/replaceslideimage.md
What replaceSlideImage does on Google Drive
AI agents use replaceSlideImage 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 |
imageUrl | string | — | Publicly accessible URL of the replacement image (use this OR localImagePath) |
imageObjectId | string | Yes | Object ID of the image to replace (from getSlideElementInfo) |
replaceMethod | string | — | How the new image fits the existing bounds (default: CENTER_INSIDE) |
localImagePath | string | — | Absolute path to a local replacement image (uploaded to Drive briefly, then cleaned up) |
presentationId | string | Yes | Presentation ID |
Parameters from the server's own tool schema.
Why replaceSlideImage is rated Medium
Modifies presentation content reversibly; image replacement is undoable via version history.
From the tool's definition Replace an existing image in place, preserving layering, position, size, and crop.
Attacks that exploit this kind of access
The rule that runs replaceSlideImage 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 replaceSlideImage, this is the rule to start with:
replaceSlideImage 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 replaceSlideImage call is checked against it from then on.
Questions about replaceSlideImage
Replace an existing image in place, preserving its layering (z-order), position, size, and crop. Unlike delete+insert, which lands the new image on top of the stack, this keeps the image under any overlaid text. 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.
replaceSlideImage accepts 6 parameters: account, imageUrl, imageObjectId, replaceMethod, localImagePath, presentationId. Required: imageObjectId, 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 replaceSlideImage: 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.
replaceSlideImage 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 replaceSlideImage 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 replaceSlideImage. 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.
replaceSlideImage 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