Request a screenshot from the browser. The screenshot will be captured asynchronously by the browser. IMPORTANT: Screenshots can take 10-15 seconds to capture (the browser must render the page to canvas). After calling this, wait 10-15 seconds, then call browser.poll to check for the screenshot ...
Handles credentials or secrets (token)
Part of the Autodock MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call browser.shot to retrieve information from Autodock without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though browser.shot only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
browser.shot:
rules:
- action: allowSee the full Autodock policy for all 27 tools.
Agents calling read-class tools like browser.shot have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Request a screenshot from the browser. The screenshot will be captured asynchronously by the browser. IMPORTANT: Screenshots can take 10-15 seconds to capture (the browser must render the page to canvas). After calling this, wait 10-15 seconds, then call browser.poll to check for the screenshot URL. If no screenshot URL is returned, wait a few more seconds and poll again. When ready, browser.poll will return a screenshotUrl. Fetch this URL to view the screenshot image and analyze what the user is seeing. Note: The browser tab must be visible for the screenshot to work.. It is categorised as a Read tool in the Autodock MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for browser.shot. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Autodock MCP server.
browser.shot 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 browser.shot 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.shot. 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.shot 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