get_visual_diff_report
Get the aggregated visual regression report from all assert_visual_match calls in this session
This record as markdown: /tools/keeveeg-godot-mcp/get-visual-diff-report.md
What get_visual_diff_report does on Godot
AI agents call get_visual_diff_report 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.
Why get_visual_diff_report is rated Low
This tool queries and returns existing test report data. It performs no modifications, deletions, code execution, or financial operations. The action is a simple read/fetch of aggregated visual regression test results, placing it squarely in the Read category with low severity since it only accesses existing test data.
From the tool's definition Tool name is 'get_visual_diff_report' and description states it retrieves/aggregates 'the visual regression report from all assert_visual_match calls in this session' — a pure data retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_visual_diff_report 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 get_visual_diff_report, this is the rule to start with:
get_visual_diff_report 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 get_visual_diff_report call is checked against it from then on.
Questions about get_visual_diff_report
Get the aggregated visual regression report from all assert_visual_match calls in this session. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP server in PolicyLayer and add a rule for get_visual_diff_report: 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.
get_visual_diff_report 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_visual_diff_report 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_visual_diff_report. 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_visual_diff_report 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