Start a browser listener to capture console logs, network requests, and errors from the user's browser. After starting, provide the user with the console command to paste in their browser. The listener will capture events until stopped or expired. USAGE: 1. Call this tool to create a listener s...
Bulk/mass operation — affects multiple targets
Part of the Autodock MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke browser.listen to trigger processes or run actions in Autodock. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
browser.listen can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
browser.listen:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Autodock policy for all 27 tools.
Agents calling execute-class tools like browser.listen have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
browser.listen is one of the high-risk operations in Autodock. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Start a browser listener to capture console logs, network requests, and errors from the user's browser. After starting, provide the user with the console command to paste in their browser. The listener will capture events until stopped or expired. USAGE: 1. Call this tool to create a listener session 2. Give the user the consoleCommand to paste in their browser console 3. IMPORTANT: Wait for the user to confirm they've pasted the command, then wait ~5 seconds for events to accumulate before calling browser.poll 4. Use browser.poll to retrieve captured events (the browser batches events every 3 seconds) 5. Use browser.shot to request a screenshot 6. Use browser.stop when done. It is categorised as a Execute tool in the Autodock MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for browser.listen. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Autodock MCP server.
browser.listen 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 browser.listen rule in your Intercept 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 Intercept policy for browser.listen. 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.listen is provided by the Autodock MCP server (mikesol/autodock). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept