upload_image
AI agents use upload_image to create or update resources in Roboflow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Roboflow MCP Server environment.
Uploading an image to a computer vision dataset platform creates or adds new data to a project. This is a Write operation—reversible and non-destructive. Severity is medium because malicious image uploads could poison training datasets, degrade model performance, or consume storage/quota, but the action itself is not destructive or irreversible (images can be removed).
From the tool's definition Tool name 'upload_image' indicates file/data creation; server context involves 'image uploads' and 'manage computer vision datasets'; sibling tools like 'download_dataset' and 'run_inference' confirm this is a dataset management platform.
Attacks that exploit this kind of access
upload_image. It is categorised as a Write tool in the Roboflow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Roboflow MCP Server MCP server in PolicyLayer and add a rule for upload_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 Roboflow MCP Server. Nothing to install.
upload_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 upload_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 upload_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.
upload_image is provided by the Roboflow MCP Server MCP server (nickedridge-wq/roboflow-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 →