High Risk →

resume_record

Resumes the record output.

How to control resume_record ↓

AI agents invoke resume_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 in OBS Studio — resuming the recording output. It has side effects on the recording state and interacts with external hardware/software, making it an Execute-category action. Misuse could lead to unintended recording, but it is not destructive or financial.

From the tool's definition Resumes the record output

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

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

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

Resumes the record 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 resume_record? +

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

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

Can I rate-limit resume_record? +

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

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

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