AI agents use imageUpload to create or update resources in Runware MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Runware MCP Server environment.
Uploading creates or stores data reversibly on a remote service, fitting the Write category. Severity is medium because uploaded images could be used downstream in generation pipelines, but the upload itself is non-destructive and doesn't directly execute code or move money. Confidence is moderate (0.75) due to empty description—we infer intent from name and server context rather than explicit documentation.
From the tool's definition Tool name 'imageUpload' combined with server context (Runware image/video generation API) indicates creation/storage of image data. Description is empty, reducing certainty.
Documented attack patterns abuse exactly the kind of access imageUpload gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Runware MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for imageUpload:
{
"version": "1",
"default": "deny",
"tools": {
"imageUpload": {
"limits": [
{
"counter": "imageupload_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}imageUpload 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.
imageUpload. It is categorised as a Write tool in the Runware MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Runware MCP Server MCP server in PolicyLayer and add a rule for imageUpload: 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 Runware MCP Server. Nothing to install.
imageUpload 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 imageUpload 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 imageUpload. 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.
imageUpload is provided by the Runware MCP Server MCP server (runware/mcp-runware). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Runware 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.
11 Runware MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.