uploads a file using a file input element
AI agents invoke upload_file to trigger actions in Mcp Selenium. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool uses Selenium WebDriver to interact with a file input element and upload a file to an external system. The effects depend on what file is uploaded and where, and the action triggers an external operation (file submission to a server/service). It is not purely a write in the local-data sense — it executes a browser action that sends data to an external endpoint.
From the tool's definition 'uploads a file using a file input element' — triggers an external file upload operation through browser automation
Attacks that exploit this kind of access
uploads a file using a file input element. It is categorised as a Execute tool in the Mcp Selenium MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Selenium 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 Mcp Selenium. Nothing to install.
upload_file is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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 Mcp Selenium MCP server (@angiejones/mcp-selenium). 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 →