This record as markdown: /tools/keeveeg-godot-mcp/set-anchor-preset.md
What set_anchor_preset does on Godot
AI agents use set_anchor_preset 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 |
|---|---|---|---|
path | string | Yes | Control node path |
preset | string | Yes | Anchor preset name (e.g. 'full_rect', 'center', 'top_left') |
Parameters from the server's own tool schema.
Why set_anchor_preset is rated Medium
This tool modifies UI control node properties (anchor preset) in a Godot scene, which is a reversible configuration change. It does not execute arbitrary code, delete data, or affect financial/external systems. The impact is limited to the visual layout configuration of a single UI control element. Classified as Write with low severity due to the contained scope and reversible nature of layout adjustments.
From the tool's definition Tool name 'set_anchor_preset' and description 'Set anchor preset on a Control node' indicate modification of UI layout properties. 'Set' is a write operation that modifies node configuration.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs set_anchor_preset 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_anchor_preset, this is the rule to start with:
set_anchor_preset 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_anchor_preset call is checked against it from then on.
Questions about set_anchor_preset
Set anchor preset on a Control node. 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_anchor_preset accepts 2 parameters: path, preset. Required: path, preset. 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_anchor_preset: 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_anchor_preset 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_anchor_preset 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_anchor_preset. 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_anchor_preset 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