compare_screenshots
Compare two screenshots pixel-by-pixel and return a diff result with mismatch percentage
This record as markdown: /tools/keeveeg-godot-mcp/compare-screenshots.md
What compare_screenshots does on Godot
AI agents call compare_screenshots to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
current | string | Yes | Path to the current screenshot |
baseline | string | Yes | Path to the baseline screenshot |
threshold | number | — | Pixel difference threshold 0-1 (default: 0.01) |
Parameters from the server's own tool schema.
Why compare_screenshots is rated Low
This tool only reads and analyzes existing screenshot files, performing a pixel-by-pixel comparison and returning a result. It does not modify, delete, or create any data, and has no side effects beyond reading input files.
From the tool's definition Compare two screenshots pixel-by-pixel and return a diff result with mismatch percentage
Attacks that exploit this kind of access
The rule that runs compare_screenshots safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compare_screenshots, this is the rule to start with:
compare_screenshots is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every compare_screenshots call is checked against it from then on.
Questions about compare_screenshots
Compare two screenshots pixel-by-pixel and return a diff result with mismatch percentage. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
compare_screenshots accepts 3 parameters: current, baseline, threshold. Required: current, baseline. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for compare_screenshots: 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 Godot. Nothing to install.
compare_screenshots 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 compare_screenshots 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 compare_screenshots. 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.
compare_screenshots is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue