physics_bake

Bake physics simulation for all objects in the scene.

SERVERBlender Copilot MCP Server SOURCEdwgx/blender-copilot

High RISK CLASS

Category Execute

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-bake.md

WHAT IT DOES

What physics_bake does on Blender Copilot MCP Server

AI agents invoke physics_bake to trigger actions in Blender Copilot MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why physics_bake is rated High

Baking a physics simulation triggers a computationally intensive operation that runs/computes physics across all scene objects, storing results into the scene data. This is an Execute-level action as it triggers an external operation (simulation computation) whose effects depend on scene state.

From the tool's definition Bake physics simulation for all objects in the scene

Attacks that exploit this kind of access

RECOMMENDED RULE

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

physics_bake Rate-limited

physics_bake stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_bake": {
      "limits": [
        {
          "counter": "physics_bake_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_bake call is checked against it from then on.

FAQ

Questions about physics_bake

What does the physics_bake tool do? +

Bake physics simulation for all objects in the scene. It is categorised as a Execute tool in the Blender Copilot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on physics_bake? +

Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for physics_bake: 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_bake? +

physics_bake is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit physics_bake? +

Yes. Add a rate_limit block to the physics_bake 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_bake completely? +

Set action: deny in the PolicyLayer policy for physics_bake. 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_bake? +

physics_bake 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →