Retrieve stored screenshot for a page. Returns file path or base64 encoded image data for AI visual analysis.
AI agents call get_page_screenshot to retrieve information from ZMCPTools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pre-existing screenshot data without side effects. While it accesses visual page content, it performs only a read operation on stored artifacts. No code execution, data modification, deletion, or external actions occur. Severity is low because screenshots contain only static visual information and pose minimal risk if accessed by an AI agent.
From the tool's definition Tool description states 'Retrieve stored screenshot' — a retrieval operation with no modification or execution of external systems. Returns file path or base64 image data for analysis only.
Documented attack patterns abuse exactly the kind of access get_page_screenshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for get_page_screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"get_page_screenshot": {}
}
}get_page_screenshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve stored screenshot for a page. Returns file path or base64 encoded image data for AI visual analysis. It is categorised as a Read tool in the ZMCPTools MCP Server, which means it retrieves data without modifying state.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for get_page_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 ZMCPTools. Nothing to install.
get_page_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 get_page_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 get_page_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.
get_page_screenshot is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.