BrowserUpload
Set files on a current BrowserObserve/BrowserFind native file-input reference. Every path must be an absolute regular file under a directory authorized for this session; this chooses files but does not submit the form or upload them by itself.
This record as markdown: /tools/dutydeck/browserupload.md
What BrowserUpload does on DutyDeck
AI agents use BrowserUpload to create or update resources in DutyDeck, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DutyDeck environment.
Why BrowserUpload is rated Medium
An AI agent can call BrowserUpload faster than any human can review: one bad instruction and it creates or modifies resources in DutyDeck by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs BrowserUpload safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DutyDeck, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For BrowserUpload, this is the rule to start with:
BrowserUpload 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.
The button opens the PolicyLayer dashboard: create your workspace, connect DutyDeck, apply this rule, and every BrowserUpload call is checked against it from then on.
Questions about BrowserUpload
Set files on a current BrowserObserve/BrowserFind native file-input reference. Every path must be an absolute regular file under a directory authorized for this session; this chooses files but does not submit the form or upload them by itself. It is categorised as a Write tool in the DutyDeck MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DutyDeck MCP server in PolicyLayer and add a rule for BrowserUpload: 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 DutyDeck. Nothing to install.
BrowserUpload 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 BrowserUpload 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 BrowserUpload. 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.
BrowserUpload is provided by the DutyDeck MCP server (taokoplay/DutyDeck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DutyDeck, and thousands of servers like it.
This server
Across the catalogue