set_tree_parameter
Set a parameter on an AnimationTree (e.g. blend amount, state)
This record as markdown: /tools/keeveeg-godot-mcp/set-tree-parameter.md
What set_tree_parameter does on Godot
AI agents use set_tree_parameter 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 | AnimationTree node path |
value | object | — | Parameter value |
parameter | string | Yes | Parameter path (e.g. 'parameters/blend_position') |
Parameters from the server's own tool schema.
Why set_tree_parameter is rated Medium
This tool modifies AnimationTree parameters, which is a write operation that changes application state. While it affects gameplay/animation behavior, the change is reversible (parameters can be adjusted back or reset), and it does not execute arbitrary code, delete data, or cause financial impact.
From the tool's definition The tool "set_tree_parameter" performs parameter modification on an AnimationTree node, changing properties like "blend amount" and "state". This is a reversible data modification operation within a game engine context.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs set_tree_parameter 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_tree_parameter, this is the rule to start with:
set_tree_parameter 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_tree_parameter call is checked against it from then on.
Questions about set_tree_parameter
Set a parameter on an AnimationTree (e.g. blend amount, state). 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_tree_parameter accepts 3 parameters: path, value, parameter. Required: path, parameter. 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_tree_parameter: 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_tree_parameter 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_tree_parameter 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_tree_parameter. 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_tree_parameter 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