ページのスクリーンショットを取得します（Base64形式）。
AI agents call browser_screenshot to retrieve information from Agent Browser MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns the current visual state of a web page as an image. It does not create, modify, delete, or execute operations that alter system state. While it runs within a browser context (which is an Execute capability of the server overall), this specific tool is a pure read operation analogous to 'get' or 'fetch'.
From the tool's definition Tool name 'browser_screenshot' and description stating it 'takes a screenshot of the page (Base64 format)' indicates a retrieval operation that captures visual state without modifying, deleting, or executing code. No side effects or state changes occur.
Attacks that exploit this kind of access
ページのスクリーンショットを取得します（Base64形式）。. It is categorised as a Read tool in the Agent Browser MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Agent Browser MCP Server 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 Agent Browser MCP Server. 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 Agent Browser MCP Server MCP server (nocall-corp/agent-browser-mcp-server). 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 →