blender_render_scene · Polybridge MCP: Risk & Policy

WHAT IT DOES

What blender_render_scene does on Polybridge MCP

AI agents invoke blender_render_scene to trigger actions in Polybridge MCP. 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 blender_render_scene needs a policy

Rendering a Blender scene triggers an external computation/operation in the Blender application. It executes a rendering process that consumes resources and produces output, but does not delete data or move money. It is more than a passive read — it actively triggers Blender's render engine.

From the tool's definition Render the current Blender scene and return the result as a base64 PNG image

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

blender_render_scene Rate-limited

blender_render_scene 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": {
    "blender_render_scene": {
      "limits": [
        {
          "counter": "blender_render_scene_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 Polybridge MCP, so you can run agents against it safely.

FAQ

Questions about blender_render_scene

What does the blender_render_scene tool do? +

Render the current Blender scene and return the result as a base64 PNG image. It is categorised as a Execute tool in the Polybridge MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on blender_render_scene? +

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

What risk level is blender_render_scene? +

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

Can I rate-limit blender_render_scene? +

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

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

blender_render_scene is provided by the Polybridge MCP server (madjeek-web/polybridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.