Bake rigid body physics simulation to keyframes for the specified frame range.
AI agents use blender_bake_physics to create or update resources in Gamedev All-in-One MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gamedev All-in-One MCP environment.
An AI agent can call blender_bake_physics faster than any human can review — one bad instruction and it creates or modifies resources in Gamedev All-in-One MCP by the hundred, each call as confident as the last.
Documented attack patterns abuse exactly the kind of access blender_bake_physics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gamedev All-in-One MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for blender_bake_physics:
{
"version": "1",
"default": "deny",
"tools": {
"blender_bake_physics": {
"limits": [
{
"counter": "blender_bake_physics_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}blender_bake_physics 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.
Free to start. No card required.
Bake rigid body physics simulation to keyframes for the specified frame range. It is categorised as a Write tool in the Gamedev All-in-One MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gamedev All-in-One MCP server in PolicyLayer and add a rule for blender_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 Gamedev All-in-One MCP. Nothing to install.
blender_bake_physics 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 blender_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 blender_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.
blender_bake_physics is provided by the Gamedev All-in-One MCP server (sansaks-jpg/gamedev-all-in-one-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 78 Gamedev All-in-One MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
78 Gamedev All-in-One MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.