New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

card_set_face

Flip an instanced card (or any node exposing set_face(bool) — the generated card and piece scripts both do) between its face and back. Instant by default: calls the setter now, so the visible side changes immediately. With animate, instead authors a reusable flip clip under the node from Group C ...

SERVERBreakpoint SOURCEbreakpoint-mcp
Medium RISK CLASS
Category Write
Parameters 42 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/card-set-face.md

What card_set_face does on Breakpoint

AI agents use card_set_face 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.

ParameterTypeRequiredDescription
node string Yes Node path of the card instance to flip (in the open scene); "." for the root
method string Setter method invoked with face_up (default "set_face"; the generated card/piece scripts expose it)
animate object Optional flip animation; omitted → an instant set_face
face_up boolean Yes Target face state: true shows the face, false the back

Parameters from the server's own tool schema.

Why card_set_face is rated Medium

The tool modifies the visual state of a node (flipping a card face/back) and optionally authors animation data. It is reversible/undoable per the description ('Undoable node authoring'), placing it in Write rather than Destructive. No code execution, financial operations, or irreversible deletions are involved.

From the tool's definition Flip an instanced card...calls the setter now, so the visible side changes immediately...authors a reusable flip clip...Undoable node authoring

Questions about card_set_face

What does the card_set_face tool do? +

Flip an instanced card (or any node exposing set_face(bool) — the generated card and piece scripts both do) between its face and back. Instant by default: calls the setter now, so the visible side changes immediately. With animate, instead authors a reusable flip clip under the node from Group C anim primitives — a scale pinch (1 → edge-on → 1) plus a method key that calls the setter at the edge-on midpoint — played on demand; purely additive (only existing node.* / anim.* ops, never a new engine call). Undoable node authoring. Returns the target state and any authored player / anim. 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_set_face accept? +

card_set_face accepts 4 parameters: node, method, animate, face_up. Required: node, face_up. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on card_set_face? +

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

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

Can I rate-limit card_set_face? +

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

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

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

More on Breakpoint, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Breakpoint's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.