tilemap_set_cell
Paint a single cell on a TileMapLayer (undoable). source_id -1 erases the cell (default). atlas_coords defaults to [0, 0]; alternative defaults to 0.
This record as markdown: /tools/breakpoint-mcp/tilemap-set-cell.md
What tilemap_set_cell does on Breakpoint
AI agents use tilemap_set_cell 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 |
|---|---|---|---|
path | string | Yes | TileMapLayer node path relative to the scene root |
coords | array | Yes | Cell coordinates [x, y] (in cells) |
source_id | integer | — | Atlas source id from the bound TileSet, or -1 to erase (default -1) |
alternative | integer | — | Alternative tile id (default 0) |
atlas_coords | array | — | Tile atlas coordinates [x, y] within the source (default [0, 0]) |
Parameters from the server's own tool schema.
Why tilemap_set_cell is rated Medium
This tool modifies tilemap cell data but is explicitly marked as undoable, making it reversible and therefore Write rather than Destructive. The blast radius is medium because an agent could paint many cells or corrupt a tilemap's visual appearance, but changes can be undone. Context (animation/tilemap editing tools) suggests this is part of a game editor or similar creative tool.
From the tool's definition Tool description states 'Paint a single cell on a TileMapLayer (undoable)', indicating reversible modification of tilemap data. The mention of 'source_id -1 erases the cell' confirms Write capability with undo support.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs tilemap_set_cell 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 tilemap_set_cell, this is the rule to start with:
tilemap_set_cell 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 tilemap_set_cell call is checked against it from then on.
Questions about tilemap_set_cell
Paint a single cell on a TileMapLayer (undoable). source_id -1 erases the cell (default). atlas_coords defaults to [0, 0]; alternative defaults to 0. 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.
tilemap_set_cell accepts 5 parameters: path, coords, source_id, alternative, atlas_coords. Required: path, coords. 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 tilemap_set_cell: 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.
tilemap_set_cell 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 tilemap_set_cell 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 tilemap_set_cell. 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.
tilemap_set_cell 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