List all supported real locations for screenshots.
AI agents call list_real_locations to retrieve information from PagePixels Screenshots MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns a static list of supported screenshot locations. It performs no data modification, execution of external commands, deletion, or financial operations. It is a straightforward informational query with minimal security risk.
From the tool's definition Tool name is 'list_real_locations' and description states it 'List all supported real locations for screenshots' — a pure query operation that retrieves configuration metadata without side effects.
Attacks that exploit this kind of access
List all supported real locations for screenshots. It is categorised as a Read tool in the PagePixels Screenshots MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PagePixels Screenshots MCP Server MCP server in PolicyLayer and add a rule for list_real_locations: 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 PagePixels Screenshots MCP Server. Nothing to install.
list_real_locations 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 list_real_locations 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 list_real_locations. 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.
list_real_locations is provided by the PagePixels Screenshots MCP Server MCP server (pagepixels/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 →