board_tile_place
Snap an existing node (a card or piece instance) onto a TileMapLayer cell by integer [x, y] tile coordinate. Undoable node authoring. The cell's local position is computed from tile_size — centre (coord + 0.5) × tile_size (default) or corner coord × tile_size — matching Godot's TileMapLayer.map_t...
This record as markdown: /tools/breakpoint-mcp/board-tile-place.md
What board_tile_place does on Breakpoint
AI agents use board_tile_place 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 |
|---|---|---|---|
node | string | Yes | Node path of the node to place (a card / piece already in the scene) |
align | object | — | Offset from the anchor in px (default 0,0) |
coord | array | Yes | Tile coordinate [x, y] (in cells) |
layer | string | Yes | TileMapLayer node path in the open scene |
anchor | string | — | Snap to the cell centre (default) or its top-left corner |
reparent | boolean | — | Reparent the node under the layer so the coordinate is layer-local (default true) |
tile_size | array | — | The layer's tile cell size [w, h] in px (default [64, 64]); must match the board's tile_size |
Parameters from the server's own tool schema.
Why board_tile_place is rated Medium
This tool creates or modifies data reversibly by repositioning and reparenting nodes in what appears to be a game engine (Godot) scene graph. The action is undoable and does not permanently destroy data. It does not execute arbitrary code, trigger external operations with unpredictable effects, or delete data.
From the tool's definition Tool description states it modifies node properties ('node.reparent + node.set_property') and explicitly describes the action as 'Undoable node authoring', indicating reversible state changes.
Attacks that exploit this kind of access
The rule that runs board_tile_place 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 board_tile_place, this is the rule to start with:
board_tile_place 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 board_tile_place call is checked against it from then on.
Questions about board_tile_place
Snap an existing node (a card or piece instance) onto a TileMapLayer cell by integer [x, y] tile coordinate. Undoable node authoring. The cell's local position is computed from tile_size — centre (coord + 0.5) × tile_size (default) or corner coord × tile_size — matching Godot's TileMapLayer.map_to_local, plus an optional align offset. With reparent (default true) the node is moved under the layer so the coordinate is layer-local. Decomposes onto node.reparent + node.set_property. Returns the node's new path and local position. 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.
board_tile_place accepts 7 parameters: node, align, coord, layer, anchor, reparent, tile_size. Required: node, coord, layer. 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 board_tile_place: 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.
board_tile_place 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 board_tile_place 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 board_tile_place. 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.
board_tile_place 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