AI agents use change_image to create or update resources in Midjourney MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Midjourney MCP Server environment.
The tool name suggests modifying an image (a write/transform operation). Given the server context of image transformations and editing, it likely creates or modifies image data. The empty description lowers confidence significantly. No evidence of destructive, financial, or execution behavior, so Write is the most appropriate category based on available context.
From the tool's definition Tool name 'change_image' on a server providing 'image transformations, advanced editing' capabilities; description is empty.
Documented attack patterns abuse exactly the kind of access change_image gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Midjourney MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for change_image:
{
"version": "1",
"default": "deny",
"tools": {
"change_image": {
"limits": [
{
"counter": "change_image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}change_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.
change_image. It is categorised as a Write tool in the Midjourney MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Midjourney MCP Server MCP server in PolicyLayer and add a rule for change_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 Midjourney MCP Server. Nothing to install.
change_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 change_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 change_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.
change_image is provided by the Midjourney MCP Server MCP server (z23cc/midjourney-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Midjourney MCP Server, 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.
7 Midjourney MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.