piece_template_create

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 122 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/piece-template-create.md

WHAT IT DOES

What piece_template_create does on Breakpoint

AI agents use piece_template_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
`art`	string	—	res:// texture bound to the Art node at build time
`back`	object	—	Optional back state; its presence makes the piece two-sided
`path`	string	Yes	Where to save the template scene, e.g. res://ui/pieces/Piece.tscn
`size`	object	Yes	Token size in px (drives the hit-area extents and, for a Control root, the Art size)
`color`	string	—	Default Art tint (self_modulate), #RRGGBB or #RRGGBBAA
`label`	boolean	—	Include a Label child for the piece name (default true)
`confirm`	boolean	—	Skip the confirmation prompt (auto-approve)
`hit_area`	object	—	Optional Area2D + CollisionShape2D for hit-testing
`overwrite`	boolean	—	Replace an existing template at `path` (default false). With overwrite omitted or false an existing `path` is REFUSED (`exists`) rather than written — before 1.
`root_type`	string	—	Root node type (default Node2D → Sprite2D art; Control → TextureRect art)
`label_text`	string	—	Static Label text shown before any data is bound
`script_path`	string	—	Generated piece script path (default derives from `path`)

Parameters from the server's own tool schema.

RISK

Why piece_template_create is rated Medium

An AI agent can call piece_template_create faster than any human can review: one bad instruction and it creates or modifies resources in Breakpoint by the hundred, each call as confident as the last.

Risk signalsAccepts file system path (path) · High parameter count (17 properties) · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

piece_template_create Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "piece_template_create": {
      "limits": [
        {
          "counter": "piece_template_create_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 piece_template_create call is checked against it from then on.

FAQ

Questions about piece_template_create

What does the piece_template_create tool do? +

Build a reusable piece (token) scene from a spec: an Art node (Sprite2D under a Node2D root, TextureRect under a Control root), an optional Label, an optional hit area (Area2D + CollisionShape2D), and an optional two-sided Back, plus a generated script-backed set_data() / set_face(). set_data binds art / color / label; set_face flips face/back visibility. DESTRUCTIVE (writes a scene + script) — gated by confirmation. Puts the editor back on the scene you had open; edited_scene names where it landed. 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 piece_template_create accept? +

piece_template_create accepts 12 parameters: art, back, path, size, color, label, confirm, hit_area, overwrite, root_type, label_text, script_path. Required: path, size. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on piece_template_create? +

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

What risk level is piece_template_create? +

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

Can I rate-limit piece_template_create? +

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

How do I block piece_template_create completely? +

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

What MCP server provides piece_template_create? +

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

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 280 Breakpoint tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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