Insert an image into a Google Doc from Drive or URL
AI agents use insert_doc_image to create or update resources in VaultAssist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VaultAssist environment.
This tool creates or modifies a Google Doc by inserting image content, which is a reversible write operation. While it changes document state, the action can be undone (image can be removed), distinguishing it from destructive operations.
From the tool's definition Tool name 'insert_doc_image' and description 'Insert an image into a Google Doc from Drive or URL' indicate modification of document content through image insertion.
Documented attack patterns abuse exactly the kind of access insert_doc_image gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VaultAssist, and nothing reaches the server without passing your rules. This is the rule we recommend for insert_doc_image:
{
"version": "1",
"default": "deny",
"tools": {
"insert_doc_image": {
"limits": [
{
"counter": "insert_doc_image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}insert_doc_image 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.
Free to start. No card required.
Insert an image into a Google Doc from Drive or URL. It is categorised as a Write tool in the VaultAssist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VaultAssist MCP server in PolicyLayer and add a rule for insert_doc_image: 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 VaultAssist. Nothing to install.
insert_doc_image 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 insert_doc_image 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 insert_doc_image. 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.
insert_doc_image is provided by the VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VaultAssist, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
79 VaultAssist tools catalogued and risk-classified — across an index of 43,000+ MCP servers.