tileset_create
Instantiate a TileSet resource and save it as a new .tres file. DESTRUCTIVE (writes a file) — gated by confirmation. tile_size is the base grid cell size in pixels (default 16×16).
This record as markdown: /tools/breakpoint-mcp/tileset-create.md
What tileset_create does on Breakpoint
AI agents use tileset_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 |
|---|---|---|---|
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
to_path | string | Yes | Destination res:// path, e.g. res://tiles/world.tres |
tile_size | array | — | Base tile grid size [x, y] in pixels (default [16, 16]) |
Parameters from the server's own tool schema.
Why tileset_create is rated Medium
While the tool creates and saves a new file (Write operation), the confirmation gate reduces the risk of accidental or malicious overwriting. If the tool could overwrite existing files without confirmation, it would be Destructive; however, the stated gating mechanism and context of creating new resources suggests this is a Write operation rather than irreversible data destruction.
From the tool's definition Tool description states it 'Instantiate a TileSet resource and save it as a new .tres file' and explicitly notes 'writes a file'.
Attacks that exploit this kind of access
The rule that runs tileset_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 tileset_create, this is the rule to start with:
tileset_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 tileset_create call is checked against it from then on.
Questions about tileset_create
Instantiate a TileSet resource and save it as a new .tres file. DESTRUCTIVE (writes a file) — gated by confirmation. tile_size is the base grid cell size in pixels (default 16×16). 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_create accepts 3 parameters: confirm, to_path, tile_size. Required: to_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_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.
tileset_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 tileset_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 tileset_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.
tileset_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