Get history of recent analysis reports.
AI agents call get_report_history to retrieve information from Screenshot Analyzer MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves previously generated analysis reports without creating, modifying, or deleting data. It is a read-only operation that queries historical data. The blast radius is minimal—an AI agent could only access existing reports it may already have permission to view. No financial, destructive, or execution risks are present.
From the tool's definition Tool name 'get_report_history' and description 'Get history of recent analysis reports' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get history of recent analysis reports. It is categorised as a Read tool in the Screenshot Analyzer MCP MCP Server, which means it retrieves data without modifying state.
Register the Screenshot Analyzer MCP server in PolicyLayer and add a rule for get_report_history: 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 Screenshot Analyzer MCP. Nothing to install.
get_report_history 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_report_history 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_report_history. 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_report_history is provided by the Screenshot Analyzer MCP server (sasuke-inu/ui-screenshot-android-review-openai). 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 →