tilemaplayer_create
Add a TileMapLayer node under a parent in the edited scene (undoable), optionally binding a TileSet .tres so cells can be painted. In-scene and undoable — not gated.
This record as markdown: /tools/godot-breakpoint-mcp/tilemaplayer-create.md
What tilemaplayer_create does on Godot Breakpoint
AI agents use tilemaplayer_create to create or update resources in Godot Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Breakpoint environment.
Why tilemaplayer_create is rated Medium
This tool creates and modifies scene data (adds a node, optionally binds resources) but the operation is explicitly undoable, making it reversible rather than destructive. It does not execute code, delete data, or move money. Write category is appropriate for reversible scene modifications.
From the tool's definition Tool creates a TileMapLayer node in the edited scene and optionally binds a TileSet resource. Description explicitly states it is 'undoable', confirming the creation is reversible. The action modifies the scene structure by adding a new node.
Attacks that exploit this kind of access
The rule that runs tilemaplayer_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tilemaplayer_create, this is the rule to start with:
tilemaplayer_create 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 Breakpoint, apply this rule, and every tilemaplayer_create call is checked against it from then on.
Questions about tilemaplayer_create
Add a TileMapLayer node under a parent in the edited scene (undoable), optionally binding a TileSet .tres so cells can be painted. In-scene and undoable — not gated. It is categorised as a Write tool in the Godot Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for tilemaplayer_create: 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 Breakpoint. Nothing to install.
tilemaplayer_create 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 tilemaplayer_create 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 tilemaplayer_create. 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.
tilemaplayer_create is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue