camera_turn · Open Brush MCP Server MCP: Risk & Policy

WHAT IT DOES

What camera_turn does on Open Brush MCP Server

AI agents invoke camera_turn to trigger actions in Open Brush 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 IT NEEDS A POLICY

Why camera_turn needs a policy

This tool sends a command to an external application (Open Brush) to rotate the camera by a relative amount. It is not a pure read, nor does it create/modify persistent data or delete anything. It executes an action in an external system whose effect depends on arguments, making Execute the best fit. Misuse has low blast radius as it only affects camera orientation in a 3D painting session.

From the tool's definition "Turns camera relatively" — triggers an external operation (camera rotation) in the Open Brush 3D painting software via the HTTP API

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

camera_turn Rate-limited

camera_turn 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": {
    "camera_turn": {
      "limits": [
        {
          "counter": "camera_turn_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 Open Brush MCP Server, so you can run agents against it safely.

FAQ

Questions about camera_turn

What does the camera_turn tool do? +

Turns camera relatively. It is categorised as a Execute tool in the Open Brush 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 camera_turn? +

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

What risk level is camera_turn? +

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

Can I rate-limit camera_turn? +

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

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

camera_turn is provided by the Open Brush MCP Server MCP server (moz411/openbrush-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

camera_turn is one line of Open Brush MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →