insertLocalImage · Google Docs & Drive MCP Server MCP

WHAT IT DOES

What insertLocalImage does on Google Docs & Drive MCP Server

AI agents use insertLocalImage to create or update resources in Google Docs & Drive MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Docs & Drive MCP Server environment.

WHY IT NEEDS A POLICY

Why insertLocalImage needs a policy

This tool performs two write operations: (1) uploading/creating an image file in Google Drive, and (2) modifying a document by inserting content. These are reversible actions—the uploaded image and insertion can be deleted or removed. While it modifies the document state, this is less severe than destructive operations (which cannot be undone) or execute operations (which run arbitrary code).

From the tool's definition Tool 'insertLocalImage' uploads a local image file to Google Drive and inserts it into a Google Document, creating new data (image file and document modification) that is reversible via deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

insertLocalImage Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "insertLocalImage": {
      "limits": [
        {
          "counter": "insertlocalimage_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google Docs & Drive MCP Server, so you can run agents against it safely.

FAQ

Questions about insertLocalImage

What does the insertLocalImage tool do? +

Uploads a local image file to Google Drive and inserts it into a Google Document. The image will be uploaded to the same folder as the document (or optionally to a specified folder). It is categorised as a Write tool in the Google Docs & Drive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on insertLocalImage? +

Register the Google Docs & Drive MCP Server MCP server in PolicyLayer and add a rule for insertLocalImage: 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 Docs & Drive MCP Server. Nothing to install.

What risk level is insertLocalImage? +

insertLocalImage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit insertLocalImage? +

Yes. Add a rate_limit block to the insertLocalImage 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 insertLocalImage completely? +

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

insertLocalImage is provided by the Google Docs & Drive MCP Server MCP server (oregpt/agenticledger_mcp_docsonly). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.