Take a screenshot of the current page or a specific element.
AI agents call Browser-Screenshot to retrieve information from MCP GitHub Login Automation Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves visual data from a webpage without altering state or data, making it fundamentally a Read operation. Severity is elevated to medium rather than low because: (1) screenshots taken during GitHub login workflows could capture authentication credentials, OAuth tokens, or other secrets in cleartext; (2) screenshots of authenticated GitHub sessions could expose private repository contents, personal…
From the tool's definition Tool name 'Browser-Screenshot' and description 'Take a screenshot of the current page or a specific element' indicate data retrieval without modification.
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 MCP GitHub Login Automation Server MCP Server, which means it retrieves data without modifying state.
Register the MCP GitHub Login Automation 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 MCP GitHub Login Automation 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 MCP GitHub Login Automation Server MCP server (nikhil-kandekar/mcp-server-demo). 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 →