Register a local file for use as a reference image in other tools (e.g. tool_transform_image).
AI agents use tool_upload_file to create or update resources in Open Google Image Generator MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Open Google Image Generator MCP environment.
The tool uploads and registers a file, which is a reversible write operation. It creates a reference/registration in the system but does not execute arbitrary code, delete data, or move money.
From the tool's definition Tool description states 'Register a local file for use as a reference image in other tools' — this creates or registers data in the system (a reference to an uploaded file) that persists for subsequent operations.
Attacks that exploit this kind of access
Register a local file for use as a reference image in other tools (e.g. tool_transform_image). It is categorised as a Write tool in the Open Google Image Generator MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Open Google Image Generator MCP server in PolicyLayer and add a rule for tool_upload_file: 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 Open Google Image Generator MCP. Nothing to install.
tool_upload_file 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 tool_upload_file 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 tool_upload_file. 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.
tool_upload_file is provided by the Open Google Image Generator MCP server (miracorhan/opengoogleimagegeneratormcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →