physics_add_rigid_body
A write tool on the Blender Copilot MCP server.
This record as markdown: /tools/dwgx-blender-copilot/physics-add-rigid-body.md
What physics_add_rigid_body does on Blender Copilot MCP Server
AI agents use physics_add_rigid_body to create or update resources in Blender Copilot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blender Copilot MCP Server environment.
Why physics_add_rigid_body is rated Medium
Based on the tool name, this likely adds a rigid body physics simulation property to a Blender object, which is a reversible modification (Write). The sibling tool 'add_rigid_body' appears similar, suggesting this is a write operation. Empty description lowers confidence; severity is medium as misuse could alter scene physics properties but is reversible.
From the tool's definition Tool name 'physics_add_rigid_body' suggests adding a rigid body physics component to an object in Blender. Description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs physics_add_rigid_body safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Blender Copilot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For physics_add_rigid_body, this is the rule to start with:
physics_add_rigid_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 Blender Copilot MCP Server, apply this rule, and every physics_add_rigid_body call is checked against it from then on.
Questions about physics_add_rigid_body
physics_add_rigid_body is a write tool on the Blender Copilot MCP Server MCP server. It is categorised as a Write tool in the Blender Copilot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for physics_add_rigid_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 Blender Copilot MCP Server. Nothing to install.
physics_add_rigid_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 physics_add_rigid_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 physics_add_rigid_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.
physics_add_rigid_body is provided by the Blender Copilot MCP Server MCP server (dwgx/blender-copilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Blender Copilot MCP Server, and thousands of servers like it.
This server
Across the catalogue