bake_physics
Bake all physics simulations in the scene to cache.
This record as markdown: /tools/dwgx-blender-copilot/bake-physics.md
What bake_physics does on Blender Copilot MCP Server
AI agents invoke bake_physics 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.
Why bake_physics is rated High
Baking physics simulations triggers a computational process that runs all physics calculations and writes results to cache. This is an Execute-category operation as it performs an active computation/simulation run with side effects (cache files written). It is not purely destructive (doesn't delete data), but it does overwrite existing cache data, making it at least Execute-level.
From the tool's definition Bake all physics simulations in the scene to cache
Attacks that exploit this kind of access
The rule that runs bake_physics 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 bake_physics, this is the rule to start with:
bake_physics 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Blender Copilot MCP Server, apply this rule, and every bake_physics call is checked against it from then on.
Questions about bake_physics
Bake all physics simulations in the scene to cache. 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.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for bake_physics: 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.
bake_physics is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the bake_physics 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 bake_physics. 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.
bake_physics 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.
Across the catalogue