Take a screenshot of the current page or a specific element
AI agents call screenshot to retrieve information from Chrome Profile MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Screenshots capture visual data from the browser without modifying state, creating, destroying, or executing arbitrary code. This is a read-only reconnaissance action. Severity is low because screenshots reveal only what is already visible to the user; an AI agent misusing this tool can gather information but cannot alter systems or data. High confidence because the function is unambiguous.
From the tool's definition Tool description states 'Take a screenshot of the current page or a specific element' — a pure observation action with no side effects. No modification, deletion, code execution, or financial operation occurs.
Attacks that exploit this kind of access
Take a screenshot of the current page or a specific element. It is categorised as a Read tool in the Chrome Profile MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chrome Profile MCP Server 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 Chrome Profile MCP Server. 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 Chrome Profile MCP Server MCP server (nghiahsgs/vibe-mcp-chrome). 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 →