tileset_add_source

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 72 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/tileset-add-source.md

WHAT IT DOES

What tileset_add_source does on Breakpoint

AI agents use tileset_add_source 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)
`margins`	array	—	Atlas margins [x, y] in pixels
`source_id`	integer	—	Explicit source id, or -1 to auto-assign (default -1)
`separation`	array	—	Atlas separation [x, y] in pixels
`texture_path`	string	Yes	Texture2D res:// path used as the atlas image
`tileset_path`	string	Yes	TileSet res:// .tres path
`texture_region_size`	array	—	Atlas cell size [x, y] in pixels (default = tile_size)

Parameters from the server's own tool schema.

RISK

Why tileset_add_source is rated Medium

Although the description includes the word 'DESTRUCTIVE', the actual operation is adding/modifying a resource file (writing), not deleting or irreversibly destroying data. The file is re-saved with new content, but this is reversible—the original tileset can be restored from version control or by removing the added source. The confirmation gate further reduces risk by requiring user approval.

From the tool's definition Tool description states it 'Add[s] a TileSetAtlasSource ... to a TileSet .tres and re-save' and explicitly notes 'writes a file'. The confirmation gate mitigates destruction risk.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

tileset_add_source Rate-limited

tileset_add_source 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_add_source": {
      "limits": [
        {
          "counter": "tileset_add_source_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_add_source call is checked against it from then on.

FAQ

Questions about tileset_add_source

What does the tileset_add_source tool do? +

Add a TileSetAtlasSource (backed by a Texture2D) to a TileSet .tres and re-save. DESTRUCTIVE (writes a file) — gated by confirmation. texture_region_size defaults to the TileSet's tile_size; source_id -1 auto-assigns. 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_add_source accept? +

tileset_add_source accepts 7 parameters: confirm, margins, source_id, separation, texture_path, tileset_path, texture_region_size. Required: texture_path, 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_add_source? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for tileset_add_source: 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_add_source? +

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

Can I rate-limit tileset_add_source? +

Yes. Add a rate_limit block to the tileset_add_source 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_add_source completely? +

Set action: deny in the PolicyLayer policy for tileset_add_source. 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_add_source? +

tileset_add_source 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

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

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