write_collision_layers
Write/overwrite 2D and 3D collision layer names in project.godot.
This record as markdown: /tools/yanhuifair-godot-mcp/write-collision-layers.md
What write_collision_layers does on Godot
AI agents use write_collision_layers 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 |
|---|---|---|---|
layers_2d | object | — | Map of layer number (e.g. "1") to display name for 2D physics |
layers_3d | object | — | Map of layer number to display name for 3D physics |
Parameters from the server's own tool schema.
Why write_collision_layers is rated Medium
Modifies project configuration file reversibly; scope limited to collision layer metadata.
From the tool's definition Write/overwrite collision layer names in project.godot
Attacks that exploit this kind of access
The rule that runs write_collision_layers 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 write_collision_layers, this is the rule to start with:
write_collision_layers 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 write_collision_layers call is checked against it from then on.
Questions about write_collision_layers
Write/overwrite 2D and 3D collision layer names in project.godot. 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.
write_collision_layers accepts 2 parameters: layers_2d, layers_3d. 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 write_collision_layers: 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.
write_collision_layers 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 write_collision_layers 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 write_collision_layers. 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.
write_collision_layers is provided by the Godot MCP server (@yanhuifair/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