stop_recording · Obs MCP: Risk & Policy

WHAT IT DOES

What stop_recording does on Obs

AI agents invoke stop_recording to trigger actions in Obs. 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 stop_recording needs a policy

While not directly destructive to data (recordings in progress are not deleted), this tool executes an operation that affects OBS Studio's state and can interrupt active recording workflows. The context shows this server controls recording, streaming, audio, and scene management—all operational state changes.

From the tool's definition The tool 'stop_recording' performs an action that triggers external operations—it controls OBS Studio's recording state via the obs-websocket plugin. Stopping a recording is an immediate action with side effects on the streaming/recording system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_recording Rate-limited

stop_recording 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": {
    "stop_recording": {
      "limits": [
        {
          "counter": "stop_recording_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 Obs, so you can run agents against it safely.

FAQ

Questions about stop_recording

What does the stop_recording tool do? +

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

How do I enforce a policy on stop_recording? +

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

What risk level is stop_recording? +

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

Can I rate-limit stop_recording? +

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

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

stop_recording is provided by the Obs MCP server (larscangit/obs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.