Take a screenshot of the current browser page
AI agents call browser_screenshot to retrieve information from ClawDaemon MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Screenshot capture is a passive observation operation with no side effects, reversible actions, code execution, data deletion, or financial impact. It retrieves visual information from the browser state. While the server context mentions 'background browser automation' suggesting broader capabilities, this specific tool is limited to visual inspection.
From the tool's definition Tool name 'browser_screenshot' and description 'Take a screenshot of the current browser page' indicate a read-only operation that captures visual state without modifying data or executing commands.
Attacks that exploit this kind of access
Take a screenshot of the current browser page. It is categorised as a Read tool in the ClawDaemon MCP MCP Server, which means it retrieves data without modifying state.
Register the ClawDaemon MCP server in PolicyLayer and add a rule for browser_screenshot: 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 ClawDaemon MCP. Nothing to install.
browser_screenshot 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_screenshot 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_screenshot. 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_screenshot is provided by the ClawDaemon MCP server (mordiaky/clawdaemon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →