card_template_create

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 113 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What card_template_create does on Breakpoint

AI agents use card_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
`back`	object	—	Optional card-back state; its presence makes the template two-sided
`face`	array	—	Slot names shown on the face; omitted → all slots
`path`	string	Yes	Where to save the template scene, e.g. res://ui/cards/Card.tscn
`size`	object	Yes	Card dimensions in px
`slots`	array	Yes	Named regions the card exposes
`theme`	object	—	Inline theme built via theme_create + theme_set_*
`confirm`	boolean	—	Auto-approve this destructive action (skip the confirmation prompt)
`overwrite`	boolean	—	Overwrite an existing template at `path` (default false)
`root_type`	string	—	Root node type (default PanelContainer)
`theme_path`	string	—	Use an existing Theme resource (res://…tres); mutually exclusive with inline theme
`script_path`	string	—	Generated card script path (default derives from `path`)

Parameters from the server's own tool schema.

RISK

Why card_template_create is rated Medium

Although the description includes the tag 'DESTRUCTIVE', the actual operation is creating new scene and script files, which are Write operations—they create and modify data reversibly. The tool does not delete, overwrite, or irreversibly destroy existing data. The confirmation gate further mitigates risk.

From the tool's definition Tool description states it "Build[s] a reusable card scene (a PackedScene) from a slot spec" and "writes a scene + script". These are creation and modification operations that are reversible.

Risk signalsAccepts file system path (path) · High parameter count (37 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

card_template_create Rate-limited

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

FAQ

Questions about card_template_create

What does the card_template_create tool do? +

Build a reusable card scene (a PackedScene) from a slot spec, with a generated script-backed set_data() / set_face(). Named slots (label / rich_text / texture / panel / badge) become the card's regions; card_instance and card_deck_from_table bind data to them by slot name. Optional inline theme and a two-sided card back. DESTRUCTIVE (writes a scene + script) — gated by confirmation. 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 card_template_create accept? +

card_template_create accepts 11 parameters: back, face, path, size, slots, theme, confirm, overwrite, root_type, theme_path, script_path. Required: path, size, slots. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on card_template_create? +

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

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

Can I rate-limit card_template_create? +

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

Set action: deny in the PolicyLayer policy for card_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 card_template_create? +

card_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 274 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 →