record_visual_regression
Record multiple frames over time for visual regression testing
This record as markdown: /tools/keeveeg-godot-mcp/record-visual-regression.md
What record_visual_regression does on Godot
AI agents use record_visual_regression to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
frames | integer | — | Number of frames to capture (default: 10) |
interval | number | — | Seconds between captures (default: 0.5) |
test_name | string | Yes | Name for this recording session |
Parameters from the server's own tool schema.
Why record_visual_regression is rated Medium
This tool writes or creates new test data (recorded frames) in a reversible manner typical of test infrastructure. It does not execute arbitrary code, destroy data, or move money. While it modifies the test data store, the operation is non-destructive and can be re-recorded or cleared.
From the tool's definition Tool name 'record_visual_regression' and description 'Record multiple frames over time for visual regression testing' indicate the tool captures and stores visual data (frames) to disk or a test database for later comparison.
Attacks that exploit this kind of access
The rule that runs record_visual_regression 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 record_visual_regression, this is the rule to start with:
record_visual_regression stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 record_visual_regression call is checked against it from then on.
Questions about record_visual_regression
Record multiple frames over time for visual regression testing. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
record_visual_regression accepts 3 parameters: frames, interval, test_name. Required: test_name. 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 record_visual_regression: 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.
record_visual_regression is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the record_visual_regression 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 record_visual_regression. 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.
record_visual_regression 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