BrowserAct
Click a current BrowserObserve/BrowserFind reference and optionally wait for one URL, visible-text, or CSS-selector condition in the same serialized operation. Prefer this to a separate click and wait when the expected condition is known.
This record as markdown: /tools/dutydeck/browseract.md
What BrowserAct does on DutyDeck
AI agents call BrowserAct to retrieve information from DutyDeck without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why BrowserAct is rated Low
Even though BrowserAct only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs BrowserAct 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 BrowserAct, this is the rule to start with:
BrowserAct is read-only, so it stays allowed. 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 BrowserAct call is checked against it from then on.
Questions about BrowserAct
Click a current BrowserObserve/BrowserFind reference and optionally wait for one URL, visible-text, or CSS-selector condition in the same serialized operation. Prefer this to a separate click and wait when the expected condition is known. It is categorised as a Read tool in the DutyDeck MCP Server, which means it retrieves data without modifying state.
Register the DutyDeck MCP server in PolicyLayer and add a rule for BrowserAct: 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.
BrowserAct is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the BrowserAct 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 BrowserAct. 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.
BrowserAct 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