AI agents use browser_file_upload to create or update resources in Wuying AgentBay — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wuying AgentBay environment.
File upload creates new data artifacts in the cloud environment and can modify the state of web applications. While reversible (files can be deleted), the action modifies system state. This is Write rather than Execute because the tool itself performs a specific, bounded operation (file upload) rather than arbitrary code execution.
From the tool's definition Tool name 'browser_file_upload' and description 'Upload one or multiple files' indicates creating/modifying data in a remote cloud environment. The sibling tools confirm this is a browser automation context within Alibaba Cloud's Wuying infrastructure.
Documented attack patterns abuse exactly the kind of access browser_file_upload gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wuying AgentBay, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_file_upload:
{
"version": "1",
"default": "deny",
"tools": {
"browser_file_upload": {
"limits": [
{
"counter": "browser_file_upload_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}browser_file_upload 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.
Upload one or multiple files. It is categorised as a Write tool in the Wuying AgentBay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wuying AgentBay MCP server in PolicyLayer and add a rule for browser_file_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 Wuying AgentBay. Nothing to install.
browser_file_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 browser_file_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 browser_file_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.
browser_file_upload is provided by the Wuying AgentBay MCP server (michael98671/agentbay). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wuying AgentBay, 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.
59 Wuying AgentBay tools catalogued and risk-classified — across an index of 43,000+ MCP servers.