set_node_preset
Apply a configuration preset to a node (e.g. 'platformer_body', 'top_down_camera')
This record as markdown: /tools/keeveeg-godot-mcp/set-node-preset.md
What set_node_preset does on Godot
AI agents use set_node_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 |
|---|---|---|---|
type | string | Yes | Node type to configure |
preset | string | Yes | Preset name to apply |
Parameters from the server's own tool schema.
Why set_node_preset is rated Medium
This tool creates or modifies node configuration reversibly by applying presets. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), and does not involve financial operations. The modification is reversible since presets can be changed or reset.
From the tool's definition The tool 'set_node_preset' applies a configuration preset to a node in Godot, which modifies node properties and settings. This is a reversible data modification operation similar to 'add_autoload_config' and 'add_audio_bus_config' present on the same server.
Attacks that exploit this kind of access
The rule that runs set_node_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_node_preset, this is the rule to start with:
set_node_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_node_preset call is checked against it from then on.
Questions about set_node_preset
Apply a configuration preset to a node (e.g. 'platformer_body', 'top_down_camera'). 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_node_preset accepts 2 parameters: type, preset. Required: type, 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_node_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_node_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_node_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_node_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_node_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