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/breakpoint-mcp/tilemaplayer-create.md
What tilemaplayer_create does on Breakpoint
AI agents use tilemaplayer_create to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Node name (default "TileMapLayer") |
parent_path | string | Yes | Parent node path relative to the scene root; "." for the root |
tileset_path | string | — | TileSet res:// .tres path to bind as tile_set (e.g. from tileset_create) |
Parameters from the server's own tool schema.
Why tilemaplayer_create is rated Medium
This tool creates and modifies scene data (adding a node and potentially binding resources) without permanently destroying data. The undoable nature confirms reversibility, placing it in Write rather than Destructive. Severity is medium because misuse could corrupt a scene's structure, but the damage is recoverable via undo functionality.
From the tool's definition Tool description states it will 'Add a TileMapLayer node under a parent in the edited scene (undoable)' and can bind a TileSet resource. The action is explicitly marked as 'undoable', indicating it modifies scene state reversibly.
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 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 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 Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
tilemaplayer_create accepts 3 parameters: name, parent_path, tileset_path. Required: parent_path. The full parameter table on this page comes from the server's own tool schema.
Register the 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 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 Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue