tileset_set_tile_collision

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 74 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/tileset-set-tile-collision.md

WHAT IT DOES

What tileset_set_tile_collision does on Breakpoint

AI agents use tileset_set_tile_collision 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)
`one_way`	boolean	—	Mark the polygon as one-way collision
`polygon`	array	Yes	Collision polygon points [[x, y], ...] (>= 3), tile-local pixels
`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
`physics_layer`	integer	—	TileSet physics layer index (default 0; created if missing)

Parameters from the server's own tool schema.

RISK

Why tileset_set_tile_collision is rated Medium

Although the description labels this 'DESTRUCTIVE' and mentions writing a file, the operation itself is reversible—collision polygons can be modified, removed, or undone. It does not irreversibly delete data or overwrite existing content in a way that cannot be recovered. The confirmation gate further mitigates risk. This is a data modification (Write) rather than destructive deletion.

From the tool's definition Tool description states 'Add a collision polygon to a tile on a TileSet physics layer and re-save' and 'DESTRUCTIVE (writes a file)'. The operation modifies a TileSet asset by adding/updating collision geometry and persists changes via file save.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tileset_set_tile_collision 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_set_tile_collision, this is the rule to start with:

tileset_set_tile_collision Rate-limited

tileset_set_tile_collision 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tileset_set_tile_collision": {
      "limits": [
        {
          "counter": "tileset_set_tile_collision_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every tileset_set_tile_collision call is checked against it from then on.

FAQ

Questions about tileset_set_tile_collision

What does the tileset_set_tile_collision tool do? +

Add a collision polygon to a tile on a TileSet physics layer and re-save. DESTRUCTIVE (writes a file) — gated by confirmation. Physics layers are created as needed. polygon is an array of [x, y] points (>= 3), tile-local pixels. 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.

What parameters does tileset_set_tile_collision accept? +

tileset_set_tile_collision accepts 7 parameters: confirm, one_way, polygon, source_id, atlas_coords, tileset_path, physics_layer. Required: polygon, source_id, atlas_coords, tileset_path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on tileset_set_tile_collision? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for tileset_set_tile_collision: 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.

What risk level is tileset_set_tile_collision? +

tileset_set_tile_collision is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit tileset_set_tile_collision? +

Yes. Add a rate_limit block to the tileset_set_tile_collision 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.

How do I block tileset_set_tile_collision completely? +

Set action: deny in the PolicyLayer policy for tileset_set_tile_collision. 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.

What MCP server provides tileset_set_tile_collision? +

tileset_set_tile_collision 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.

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 274 Breakpoint tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →