card_hand_layout

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 114 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/card-hand-layout.md

WHAT IT DOES

What card_hand_layout does on Breakpoint

AI agents use card_hand_layout 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
`mode`	string	Yes	Arrangement mode
`align`	string	—	Alignment along the layout (default center)
`cards`	array	Yes	One entry per card to instance
`origin`	object	—	Top-left origin offset in px
`parent`	string	Yes	Container node path the cards are instanced under; "." for the root
`columns`	integer	—	Grid mode column count
`overlap`	number	—	px overlap (row / fan / stack)
`persist`	boolean	—	Bake each card's bound slot data into the saved scene by enabling Editable Children on every instanced card (default false = runtime-bound only, reverts on relo
`spacing`	number	—	px between cards (row / grid)
`fan_angle`	number	—	Total fan spread in degrees (fan mode)
`template_path`	string	Yes	Card template scene, e.g. res://ui/cards/Card.tscn

Parameters from the server's own tool schema.

RISK

Why card_hand_layout is rated Medium

This tool creates and modifies card UI instances and their layout properties. While the changes are marked as undoable (reversible), the tool's primary function is to write/create new data structures and modify existing ones—classic Write category behavior. It does not execute arbitrary code, delete irreversibly, or move financial assets, so more severe categories do not apply.

From the tool's definition The tool 'Instance N cards under a container and arrange them' creates UI elements and modifies their layout state. The description explicitly states 'Undoable node authoring', confirming it writes/creates data structure changes.

Risk signalsHigh parameter count (15 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

card_hand_layout Rate-limited

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

FAQ

Questions about card_hand_layout

What does the card_hand_layout tool do? +

Instance N cards under a container and arrange them as a row, fan, stack, or grid. Undoable node authoring. Each card carries its own data (bound via the template's set_data) and face state; spacing / overlap / fan_angle / columns / align / origin tune the arrangement. 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_hand_layout accept? +

card_hand_layout accepts 11 parameters: mode, align, cards, origin, parent, columns, overlap, persist, spacing, fan_angle, template_path. Required: mode, cards, parent, template_path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on card_hand_layout? +

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

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

Can I rate-limit card_hand_layout? +

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

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

card_hand_layout 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

The MCP Attack Database →

Guides

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