Save a base64-encoded image to a file.
AI agents use save_image to create or update resources in Image Generation MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Image Generation MCP Server environment.
This tool writes data to the filesystem by persisting image files. While not destructive (files can be overwritten or deleted separately), and not dangerous by itself, it has medium severity because uncontrolled file writes could fill disk space, overwrite important files, or create unwanted artifacts.
From the tool's definition Tool name is 'save_image' and description states it saves a 'base64-encoded image to a file', which creates or modifies files on disk.
Attacks that exploit this kind of access
Save a base64-encoded image to a file. It is categorised as a Write tool in the Image Generation MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Image Generation MCP Server MCP server in PolicyLayer and add a rule for save_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 Image Generation MCP Server. Nothing to install.
save_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 save_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 save_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.
save_image is provided by the Image Generation MCP Server MCP server (marc-shade/image-gen-mcp). 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 →