Capture a screenshot of any webpage. Returns the image as base64-encoded data.
AI agents call screenshot to retrieve information from Junipr MCP Server 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 information retrieval action. It accesses and returns data (visual rendering of a webpage) without creating, modifying, deleting, or executing operations. The base64 encoding is merely a data format transformation. No side effects or state changes occur on the target system. This aligns with the Read category definition: 'retrieves or queries data; no side effects.'
From the tool's definition Tool description states 'Capture a screenshot of any webpage. Returns the image as base64-encoded data.' This is a read-only operation that retrieves visual data without modifying, executing code, or causing destructive side effects.
Attacks that exploit this kind of access
Capture a screenshot of any webpage. Returns the image as base64-encoded data. It is categorised as a Read tool in the Junipr MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Junipr 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 Junipr 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 Junipr MCP Server MCP server (junipr-labs/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 →