New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

getGoogleDocImage

Fetch the bytes of an inline image embedded in a Google Doc, keyed by its inline object ID. Returns a native image the model can see (or base64). The doc is re-fetched so the underlying image URL is always fresh — pass the objectId, never a raw contentUri (those expire). Inline images only; float...

SERVERGoogle Drive SOURCE@ark7/google-drive-mcp
Low RISK CLASS
Category Read
Parameters 42 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ark7-google-drive-mcp/getgoogledocimage.md

What getGoogleDocImage does on Google Drive

AI agents call getGoogleDocImage to retrieve information from Google Drive without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
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
documentId string Yes Document ID
outputFormat string — "image" (default) returns a native MCP image block the model can view; "base64" returns a JSON envelope { inlineObjectId, mimeType, byteLength, dataBase64 } for
inlineObjectId string Yes The inline object ID shown in readGoogleDoc / getGoogleDocContent image placeholders (the objectId=... value, e.g. "kix.abc123")

Parameters from the server's own tool schema.

Why getGoogleDocImage is rated Low

This tool retrieves image data from Google Docs and returns it for viewing. It performs a read-only operation—fetching and displaying content that already exists. There is no creation, modification, deletion, code execution, or financial impact. The re-fetching of the document to ensure fresh URLs does not constitute a side effect that would elevate the classification beyond Read.

From the tool's definition Tool name 'getGoogleDocImage' and description 'Fetch the bytes of an inline image' indicates retrieval of existing data with no modification or side effects.

Questions about getGoogleDocImage

What does the getGoogleDocImage tool do? +

Fetch the bytes of an inline image embedded in a Google Doc, keyed by its inline object ID. Returns a native image the model can see (or base64). The doc is re-fetched so the underlying image URL is always fresh — pass the objectId, never a raw contentUri (those expire). Inline images only; floating/anchored images are not supported. It is categorised as a Read tool in the Google Drive MCP Server, which means it retrieves data without modifying state.

What parameters does getGoogleDocImage accept? +

getGoogleDocImage accepts 4 parameters: account, documentId, outputFormat, inlineObjectId. Required: documentId, inlineObjectId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on getGoogleDocImage? +

Register the Google Drive MCP server in PolicyLayer and add a rule for getGoogleDocImage: 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.

What risk level is getGoogleDocImage? +

getGoogleDocImage is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getGoogleDocImage? +

Yes. Add a rate_limit block to the getGoogleDocImage 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.

How do I block getGoogleDocImage completely? +

Set action: deny in the PolicyLayer policy for getGoogleDocImage. 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.

What MCP server provides getGoogleDocImage? +

getGoogleDocImage 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Google Drive's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.