bake_ambient_occlusion · Blender MCP: Risk & Policy

WHAT IT DOES

What bake_ambient_occlusion does on BlenderMCP

AI agents invoke bake_ambient_occlusion to trigger actions in BlenderMCP. 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 IT NEEDS A POLICY

Why bake_ambient_occlusion needs a policy

Baking ambient occlusion in Blender is a compute-intensive rendering operation that executes within the Blender environment, triggering GPU/CPU processing to generate AO maps. It likely modifies scene data or image textures as a side effect.

From the tool's definition Tool name 'bake_ambient_occlusion' and server context of Blender integration with Python script execution

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bake_ambient_occlusion Rate-limited

bake_ambient_occlusion 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": {
    "bake_ambient_occlusion": {
      "limits": [
        {
          "counter": "bake_ambient_occlusion_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches BlenderMCP, so you can run agents against it safely.

FAQ

Questions about bake_ambient_occlusion

What does the bake_ambient_occlusion tool do? +

bake_ambient_occlusion. It is categorised as a Execute tool in the BlenderMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on bake_ambient_occlusion? +

Register the Blender MCP server in PolicyLayer and add a rule for bake_ambient_occlusion: 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 BlenderMCP. Nothing to install.

What risk level is bake_ambient_occlusion? +

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

Can I rate-limit bake_ambient_occlusion? +

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

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

bake_ambient_occlusion is provided by the Blender MCP server (shirshovdim/retopoflow_blender_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.