insert_image_from_url · LLM2Docs (Unofficial) MCP

WHAT IT DOES

What insert_image_from_url does on LLM2Docs (Unofficial)

AI agents use insert_image_from_url to create or update resources in LLM2Docs (Unofficial) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LLM2Docs (Unofficial) environment.

WHY IT NEEDS A POLICY

Why insert_image_from_url needs a policy

The tool creates/adds new content (an image) to an existing document, which is a write operation. It is reversible (the image can be deleted), so it does not qualify as Destructive. The severity is medium because inserting unexpected or malicious images could deface documents or inject unwanted content, but the impact is limited to document appearance and can be undone.

From the tool's definition Tool name 'insert_image_from_url' and description 'Insert an image into the document from a URL' indicate modification of document content. This is a reversible write operation that adds content to a Google Docs document.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

insert_image_from_url Rate-limited

insert_image_from_url 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": {
    "insert_image_from_url": {
      "limits": [
        {
          "counter": "insert_image_from_url_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 LLM2Docs (Unofficial), so you can run agents against it safely.

FAQ

Questions about insert_image_from_url

What does the insert_image_from_url tool do? +

Insert an image into the document from a URL. It is categorised as a Write tool in the LLM2Docs (Unofficial) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on insert_image_from_url? +

Register the LLM2Docs (Unofficial) MCP server in PolicyLayer and add a rule for insert_image_from_url: 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 LLM2Docs (Unofficial). Nothing to install.

What risk level is insert_image_from_url? +

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

Can I rate-limit insert_image_from_url? +

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

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

insert_image_from_url is provided by the LLM2Docs (Unofficial) MCP server (nomannayeem/google-docs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.