center_camera · OBSBOT Camera MCP Server MCP: Risk & Policy

WHAT IT DOES

What center_camera does on OBSBOT Camera MCP Server

AI agents invoke center_camera to trigger actions in OBSBOT Camera 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 center_camera needs a policy

This tool triggers an external physical operation — repositioning a PTZ camera gimbal to its center position. It causes a real-world side effect (camera movement) that depends on the connected hardware. It is not merely reading data, but actively commanding the camera, placing it in the Execute category.

From the tool's definition Return camera to center position (pan=0, tilt=0, zoom=0)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

center_camera Rate-limited

center_camera 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": {
    "center_camera": {
      "limits": [
        {
          "counter": "center_camera_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 OBSBOT Camera MCP Server, so you can run agents against it safely.

FAQ

Questions about center_camera

What does the center_camera tool do? +

Return camera to center position (pan=0, tilt=0, zoom=0). It is categorised as a Execute tool in the OBSBOT Camera 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 center_camera? +

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

What risk level is center_camera? +

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

Can I rate-limit center_camera? +

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

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

center_camera is provided by the OBSBOT Camera MCP Server MCP server (radar105/obsbot-camera-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

center_camera is one line of OBSBOT Camera 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 →