Take a screenshot of a URL or render HTML/Markdown and return the image.
AI agents call screenshot to retrieve information from SnapAPI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool captures and returns data (an image) without side effects. It does not create, modify, delete, or execute code/commands. It is purely observational — analogous to a read operation. The low severity reflects that misuse would primarily result in unwanted information disclosure rather than system compromise, financial loss, or data destruction.
From the tool's definition Tool description states 'Take a screenshot of a URL or render HTML/Markdown and return the image' — the core function is to retrieve a visual representation of a web page without modifying, deleting, or executing actions on external systems.
Attacks that exploit this kind of access
Take a screenshot of a URL or render HTML/Markdown and return the image. It is categorised as a Read tool in the SnapAPI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SnapAPI 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 SnapAPI 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 SnapAPI MCP Server MCP server (sleywill/snapapi-mcp). 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 →