insertSlidesLocalImage
Upload a local image file to Google Drive and insert it into a Google Slides slide
This record as markdown: /tools/ark7-google-drive-mcp/insertslideslocalimage.md
What insertSlidesLocalImage does on Google Drive
AI agents use insertSlidesLocalImage 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 | — | X position in EMU (default: 0) |
y | number | — | Y position in EMU (default: 0) |
width | number | — | Width in EMU (omit to auto-size) |
height | number | — | Height in EMU (omit to auto-size) |
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 |
pageObjectId | string | Yes | Slide/page object ID to insert the image into |
localImagePath | string | Yes | Absolute path to the local image file |
presentationId | string | Yes | Presentation ID |
Parameters from the server's own tool schema.
Why insertSlidesLocalImage is rated Medium
This tool creates new data (uploads an image file) and modifies existing data (inserts into a slide), both reversible operations typical of Write category. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool description states it will 'Upload a local image file to Google Drive and insert it into a Google Slides slide' — these are create/modify operations that add new content to cloud storage and presentations.
Attacks that exploit this kind of access
The rule that runs insertSlidesLocalImage 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 insertSlidesLocalImage, this is the rule to start with:
insertSlidesLocalImage 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 insertSlidesLocalImage call is checked against it from then on.
Questions about insertSlidesLocalImage
Upload a local image file to Google Drive and insert it into 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.
insertSlidesLocalImage accepts 8 parameters: x, y, width, height, account, pageObjectId, localImagePath, presentationId. Required: pageObjectId, localImagePath, 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 insertSlidesLocalImage: 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.
insertSlidesLocalImage 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 insertSlidesLocalImage 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 insertSlidesLocalImage. 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.
insertSlidesLocalImage 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