body_create
Add a physics body node under a parent in the edited scene (undoable): a StaticBody, RigidBody, CharacterBody, or Area, in 2D or 3D. In-scene and undoable — not gated. Attach collision shapes with collisionshape_add.
This record as markdown: /tools/breakpoint-mcp/body-create.md
What body_create does on Breakpoint
AI agents use body_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 |
|---|---|---|---|
dim | string | — | Dimension: "2d" (default) or "3d" |
name | string | — | Node name (default the class name, e.g. "StaticBody2D") |
type | string | Yes | Body kind: static | rigid | character | area |
parent_path | string | Yes | Parent node path relative to the scene root; "." for the root |
Parameters from the server's own tool schema.
Why body_create is rated Medium
This tool creates physics body nodes in a scene, which is a write operation that modifies the game/scene structure. While marked as 'undoable', the primary effect is data creation/modification rather than deletion or code execution.
From the tool's definition Tool description states 'Add a physics body node' and 'undoable', indicating it creates and modifies scene data reversibly. The phrase 'In-scene and undoable' confirms the operation can be reversed.
Attacks that exploit this kind of access
The rule that runs body_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 body_create, this is the rule to start with:
body_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every body_create call is checked against it from then on.
Questions about body_create
Add a physics body node under a parent in the edited scene (undoable): a StaticBody, RigidBody, CharacterBody, or Area, in 2D or 3D. In-scene and undoable — not gated. Attach collision shapes with collisionshape_add. 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.
body_create accepts 4 parameters: dim, name, type, parent_path. Required: type, parent_path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for body_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.
body_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the body_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.
Set action: deny in the PolicyLayer policy for body_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.
body_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.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue