This record as markdown: /tools/keeveeg-godot-mcp/setup-physics-body.md
What setup_physics_body does on Godot
AI agents use setup_physics_body to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Node to add the physics body to |
properties | object | Yes | Body properties (mass, gravity_scale, etc.) |
Parameters from the server's own tool schema.
Why setup_physics_body is rated Medium
This tool creates and configures a new physics body component in the Godot engine, which modifies the scene structure reversibly. It falls under Write rather than Execute because it's a declarative scene composition operation, not arbitrary code execution. Severity is medium because misconfiguration could affect game physics behavior, but the operation is reversible—the physics body can be removed or reconfigured.
From the tool's definition Tool name 'setup_physics_body' combined with description 'Add and configure a physics body on a node' indicates creation and modification of scene graph elements in Godot.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs setup_physics_body safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For setup_physics_body, this is the rule to start with:
setup_physics_body 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 Godot, apply this rule, and every setup_physics_body call is checked against it from then on.
Questions about setup_physics_body
Add and configure a physics body on a node. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
setup_physics_body accepts 2 parameters: path, properties. Required: path, properties. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for setup_physics_body: 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 Godot. Nothing to install.
setup_physics_body 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 setup_physics_body 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 setup_physics_body. 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.
setup_physics_body is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue