set_visual_baseline
Set or update a visual baseline for future comparisons
This record as markdown: /tools/keeveeg-godot-mcp/set-visual-baseline.md
What set_visual_baseline does on Godot
AI agents use set_visual_baseline 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 |
|---|---|---|---|
name | string | Yes | Baseline name identifier |
screenshot_path | string | Yes | Path to the screenshot to use as baseline |
Parameters from the server's own tool schema.
Why set_visual_baseline is rated Medium
This tool creates or modifies a visual baseline configuration, which is a reversible data change. It does not execute code, delete data irreversibly, or move money. While it affects project state, the operation can be undone or overwritten by setting a new baseline.
From the tool's definition Tool name 'set_visual_baseline' and description 'Set or update a visual baseline' indicate data modification operations.
Attacks that exploit this kind of access
The rule that runs set_visual_baseline 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 set_visual_baseline, this is the rule to start with:
set_visual_baseline 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 set_visual_baseline call is checked against it from then on.
Questions about set_visual_baseline
Set or update a visual baseline for future comparisons. 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.
set_visual_baseline accepts 2 parameters: name, screenshot_path. Required: name, screenshot_path. 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 set_visual_baseline: 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.
set_visual_baseline 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 set_visual_baseline 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 set_visual_baseline. 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.
set_visual_baseline 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