High Risk →

stop_record

Stops the record output. Returns: Dict containing the output path of the stopped recording

How to control stop_record ↓

AI agents invoke stop_record to trigger actions in OBS 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.

High Risk

This tool triggers an external operation (halting OBS recording) whose effects depend on the current state of the OBS application. While not destructive (the recorded file is preserved) or financial, it executes a command that changes system state and could interrupt critical streaming/recording workflows if misused by an agent.

From the tool's definition Tool name 'stop_record' and description 'Stops the record output' indicate an action that terminates an ongoing recording operation, which is a state-changing external operation.

Documented attack patterns abuse exactly the kind of access stop_record gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and OBS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_record:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_record": {
      "limits": [
        {
          "counter": "stop_record_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register OBS MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the stop_record tool do? +

Stops the record output. Returns: Dict containing the output path of the stopped recording. It is categorised as a Execute tool in the OBS 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 stop_record? +

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

What risk level is stop_record? +

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

Can I rate-limit stop_record? +

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

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

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

Enforce policy on every OBS MCP Server tool call.

Deterministic rules across all 200 OBS MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

200 OBS MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.