Take a screenshot of the current page (use fullPage for the entire scrollable length)
AI agents call screenshot to retrieve information from Chromium ARM64 Browser without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A screenshot is a read-only operation that retrieves the visual representation of a webpage. It has no side effects, does not execute code or scripts, does not modify data, and does not delete or destroy resources. This is a pure information-retrieval action, making it the lowest-risk category.
From the tool's definition Tool description states 'Take a screenshot of the current page' — captures visual content without modification, creation, or deletion. No parameters enable state changes, code execution, or data alteration.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Take a screenshot of the current page (use fullPage for the entire scrollable length). It is categorised as a Read tool in the Chromium ARM64 Browser MCP Server, which means it retrieves data without modifying state.
Register the Chromium ARM64 Browser MCP server in PolicyLayer and add a rule for 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 Chromium ARM64 Browser. Nothing to install.
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 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 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.
screenshot is provided by the Chromium ARM64 Browser MCP server (nfodor/mcp-chromium-arm64). 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 →