physics_add_collision

Add collision physics to an object (makes it a collider for cloth/particles).

SERVERBlender Copilot MCP Server SOURCEdwgx/blender-copilot

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dwgx-blender-copilot/physics-add-collision.md

WHAT IT DOES

What physics_add_collision does on Blender Copilot MCP Server

AI agents use physics_add_collision 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.

RISK

Why physics_add_collision is rated Medium

This tool modifies object properties by adding a collision physics component, fitting the Write category. It is not Destructive (reversible), not Financial, not Execute (does not run arbitrary code), and not Read (creates side effects). Severity is medium because misuse could create unwanted physics behaviors affecting a 3D scene, but the impact is limited to the current project and fully reversible.

From the tool's definition Adds collision physics to an object, which modifies the object's properties to make it a collider. This is a state change in the 3D scene (adding a physics component) that is reversible (collision properties can be removed or changed).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs physics_add_collision 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_collision, this is the rule to start with:

physics_add_collision Rate-limited

physics_add_collision 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "physics_add_collision": {
      "limits": [
        {
          "counter": "physics_add_collision_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Blender Copilot MCP Server, apply this rule, and every physics_add_collision call is checked against it from then on.

FAQ

Questions about physics_add_collision

What does the physics_add_collision tool do? +

Add collision physics to an object (makes it a collider for cloth/particles). 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.

How do I enforce a policy on physics_add_collision? +

Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for physics_add_collision: 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.

What risk level is physics_add_collision? +

physics_add_collision is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit physics_add_collision? +

Yes. Add a rate_limit block to the physics_add_collision 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.

How do I block physics_add_collision completely? +

Set action: deny in the PolicyLayer policy for physics_add_collision. 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.

What MCP server provides physics_add_collision? +

physics_add_collision 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.

KEEP EXPLORING

More on Blender Copilot MCP Server, and thousands of servers like it.

This server

All 307 Blender Copilot MCP Server tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb →add_video on Mcptube Vision → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →