AI agents call diagnose_error_screenshot to retrieve information from Vison-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and interprets visual information from screenshots—specifically error messages and stack traces—to help diagnose issues. It has no side effects beyond reading and analyzing image data. While it could theoretically extract sensitive information visible in screenshots (low severity), it performs pure analysis without executing code, modifying systems, or deleting data.
From the tool's definition The tool analyzes error screenshots and appears to perform OCR or image analysis on error messages, stack traces, and build output.
Attacks that exploit this kind of access
Analyze error screenshots (build errors, runtime errors, stack traces) and. It is categorised as a Read tool in the Vison-MCP MCP Server, which means it retrieves data without modifying state.
Register the Vison- MCP server in PolicyLayer and add a rule for diagnose_error_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 Vison-MCP. Nothing to install.
diagnose_error_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 diagnose_error_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 diagnose_error_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.
diagnose_error_screenshot is provided by the Vison- MCP server (lin-zhibo/vison-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 →