tileset_add_tile
Create a tile at atlas_coords in an atlas source of a TileSet .tres and re-save. DESTRUCTIVE (writes a file) — gated by confirmation. size is measured in atlas cells (default [1, 1]).
This record as markdown: /tools/breakpoint-mcp/tileset-add-tile.md
What tileset_add_tile does on Breakpoint
AI agents use tileset_add_tile 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 |
|---|---|---|---|
size | array | — | Tile size in atlas cells [x, y] (default [1, 1]) |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
source_id | integer | Yes | Atlas source id within the TileSet |
atlas_coords | array | Yes | Tile atlas coordinates [x, y] (in cells) |
tileset_path | string | Yes | TileSet res:// .tres path |
Parameters from the server's own tool schema.
Why tileset_add_tile is rated Medium
While the description uses the word 'DESTRUCTIVE', the actual operation is creating/adding a new tile to an existing tileset file, which is a reversible modification rather than irreversible deletion or data destruction. The file write is gated by confirmation, further reducing risk.
From the tool's definition Tool description explicitly states 'Create a tile at atlas_coords in an atlas source of a TileSet .tres and re-save' and acknowledges 'DESTRUCTIVE (writes a file) — gated by confirmation'
Attacks that exploit this kind of access
The rule that runs tileset_add_tile 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 tileset_add_tile, this is the rule to start with:
tileset_add_tile 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 tileset_add_tile call is checked against it from then on.
Questions about tileset_add_tile
Create a tile at atlas_coords in an atlas source of a TileSet .tres and re-save. DESTRUCTIVE (writes a file) — gated by confirmation. size is measured in atlas cells (default [1, 1]). 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.
tileset_add_tile accepts 5 parameters: size, confirm, source_id, atlas_coords, tileset_path. Required: source_id, atlas_coords, tileset_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 tileset_add_tile: 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.
tileset_add_tile 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 tileset_add_tile 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 tileset_add_tile. 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.
tileset_add_tile 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