High Risk →

start_replay_buffer

Starts the replay buffer output.

How to control start_replay_buffer ↓

AI agents invoke start_replay_buffer 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 executes a command that initiates a recording subsystem in OBS Studio. While not destructive or financial, it is an Execute action because it triggers an external operation with real-world side effects (consuming system resources, initiating recording).

From the tool's definition Tool description states 'Starts the replay buffer output' — this triggers an external operation (OBS replay buffer activation) whose effects depend on the OBS configuration and system state.

Documented attack patterns abuse exactly the kind of access start_replay_buffer 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 start_replay_buffer:

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

start_replay_buffer 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 start_replay_buffer tool do? +

Starts the replay buffer output. 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 start_replay_buffer? +

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

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

Can I rate-limit start_replay_buffer? +

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

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

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