Upload files to a <input type=\
AI agents use browserbeam_upload to create or update resources in Browserbeam MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Browserbeam MCP Server environment.
File upload is a Write action—it creates or stores data on a remote server. Severity is high because uncontrolled file uploads could be exploited to upload malicious files, overwrite existing files, or consume storage resources. However, it is not Destructive (reversible) or Execute (code execution), and the description is truncated making precise assessment difficult, slightly lowering confidence.
From the tool's definition Tool name 'browserbeam_upload' and description 'Upload files to a <input type=' indicates file upload functionality to web form inputs. This is a write operation that modifies server state by storing user-supplied files.
Attacks that exploit this kind of access
Upload files to a <input type=\. It is categorised as a Write tool in the Browserbeam MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Browserbeam MCP Server MCP server in PolicyLayer and add a rule for browserbeam_upload: 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 Browserbeam MCP Server. Nothing to install.
browserbeam_upload 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 browserbeam_upload 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 browserbeam_upload. 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.
browserbeam_upload is provided by the Browserbeam MCP Server MCP server (nyku/browserbeam-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 →