physics_set_body_properties
A write tool on the Godot MCP server.
This record as markdown: /tools/chanceflow-godot-mcp/physics-set-body-properties.md
What physics_set_body_properties does on Godot
AI agents use physics_set_body_properties 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.
Why physics_set_body_properties is rated Medium
This tool modifies physics body properties in the Godot engine, which is a reversible write operation. While the exact scope is unclear due to empty description, it aligns with configuration/update patterns seen in sibling tools. Severity is medium because incorrect physics property changes could affect game behavior and simulation, but effects are contained to the game engine instance and are reversible.
From the tool's definition Tool name 'physics_set_body_properties' indicates modification of physics object properties. The description is empty, but context from sibling tools (audio_configure_bus, animation_set_keyframe, autoload_add) shows this server uses 'set_' and 'configure_'…
Attacks that exploit this kind of access
The rule that runs physics_set_body_properties 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 physics_set_body_properties, this is the rule to start with:
physics_set_body_properties 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 physics_set_body_properties call is checked against it from then on.
Questions about physics_set_body_properties
physics_set_body_properties is a write tool on the Godot MCP server. 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.
Register the Godot MCP server in PolicyLayer and add a rule for physics_set_body_properties: 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.
physics_set_body_properties 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 physics_set_body_properties 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 physics_set_body_properties. 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.
physics_set_body_properties is provided by the Godot MCP server (chanceflow/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