create_vehicle_body
Create a VehicleBody3D with VehicleWheel nodes for car physics.
This record as markdown: /tools/yanhuifair-godot-mcp/create-vehicle-body.md
What create_vehicle_body does on Godot
AI agents use create_vehicle_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 |
|---|---|---|---|
name | object | — | |
parent | object | — | |
wheels | object | — | |
scene_path | string | Yes |
Parameters from the server's own tool schema.
Why create_vehicle_body is rated Medium
The tool creates new game objects (VehicleBody3D nodes and child VehicleWheel nodes) within a Godot scene, which is a Write operation—it modifies the project state but can be undone (deleted). It does not execute arbitrary code, delete data irreversibly, or trigger external side effects beyond the Godot editor itself.
From the tool's definition Tool name 'create_vehicle_body' and description 'Create a VehicleBody3D with VehicleWheel nodes' explicitly indicates creation of scene nodes in Godot Engine. This is a reversible modification to the game project structure.
Attacks that exploit this kind of access
The rule that runs create_vehicle_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 create_vehicle_body, this is the rule to start with:
create_vehicle_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 create_vehicle_body call is checked against it from then on.
Questions about create_vehicle_body
Create a VehicleBody3D with VehicleWheel nodes for car physics. 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.
create_vehicle_body accepts 4 parameters: name, parent, wheels, scene_path. Required: scene_path. 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 create_vehicle_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.
create_vehicle_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 create_vehicle_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 create_vehicle_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.
create_vehicle_body is provided by the Godot MCP server (@yanhuifair/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