spectator_move · Open Brush MCP Server MCP: Risk & Policy

WHAT IT DOES

What spectator_move does on Open Brush MCP Server

AI agents use spectator_move to create or update resources in Open Brush MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Open Brush MCP Server environment.

WHY IT NEEDS A POLICY

Why spectator_move needs a policy

This tool moves the spectator camera position in the Open Brush 3D painting software. It modifies the state of the application (camera position) but does not delete data, execute arbitrary code, or have financial implications. It is reversible as the camera can be moved back. Severity is low as misuse only affects the viewing perspective within the application.

From the tool's definition Moves spectator camera

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

spectator_move Rate-limited

spectator_move 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "spectator_move": {
      "limits": [
        {
          "counter": "spectator_move_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 spectator_move

What does the spectator_move tool do? +

Moves spectator camera. It is categorised as a Write tool in the Open Brush MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on spectator_move? +

Register the Open Brush MCP Server MCP server in PolicyLayer and add a rule for spectator_move: 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 spectator_move? +

spectator_move is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit spectator_move? +

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

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

spectator_move 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.