This record as markdown: /tools/keeveeg-godot-mcp/batch-set-property.md
What batch_set_property does on Godot
AI agents use batch_set_property 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 |
|---|---|---|---|
value | object | — | Property value |
property | string | Yes | Property name (e.g. 'position', 'visible') |
type_name | string | Yes | Node type name (e.g. 'Sprite2D', 'CharacterBody3D') |
Parameters from the server's own tool schema.
Why batch_set_property is rated Medium
The tool performs bulk property updates across multiple nodes, which is a reversible modification (Write category). The severity is high because a single misuse could alter many nodes at once, affecting game logic, rendering, physics, or other critical systems across the project.
From the tool's definition Tool name 'batch_set_property' and description 'Set a property on all nodes of a given type' indicates bulk modification of node properties in a Godot project. This is a Write operation that modifies data (node properties) reversibly.
Attacks that exploit this kind of access
The rule that runs batch_set_property 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 batch_set_property, this is the rule to start with:
batch_set_property 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 batch_set_property call is checked against it from then on.
Questions about batch_set_property
Set a property on all nodes of a given type. 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.
batch_set_property accepts 3 parameters: value, property, type_name. Required: property, type_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 batch_set_property: 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.
batch_set_property 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 batch_set_property 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 batch_set_property. 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.
batch_set_property 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