Upload a local file into a file input using selector or element id.
AI agents use upload_file to create or update resources in Visual Annotation MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Visual Annotation MCP environment.
The tool modifies application state by submitting file data through an input element, making it a Write operation. Severity is medium because the impact depends on what the receiving system does with the uploaded file (could range from harmless to harmful depending on the application context and file type), and an LLM could inadvertently upload sensitive files or malicious content if not properly constrained.
From the tool's definition Tool description states 'Upload a local file into a file input', which creates data (file submission) in a web form or system without deletion or financial transaction.
Attacks that exploit this kind of access
Upload a local file into a file input using selector or element id. It is categorised as a Write tool in the Visual Annotation MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Visual Annotation MCP server in PolicyLayer and add a rule for 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 Visual Annotation MCP. Nothing to install.
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 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 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.
upload_file is provided by the Visual Annotation MCP server (mstocker1/visual_annotation_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 →