Toggles pause on the record output. Returns: Whether the output is paused after toggling
AI agents invoke toggle_record_pause 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.
This tool controls the recording state in OBS by pausing/unpausing an active recording session. It triggers an external operation (modifying the state of OBS recording) that affects ongoing capture. It's not destructive (no data is deleted), not a simple read, and not a write of new data — it's execution of a control action on a live external process.
From the tool's definition Toggles pause on the record output
Documented attack patterns abuse exactly the kind of access toggle_record_pause 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 toggle_record_pause:
{
"version": "1",
"default": "deny",
"tools": {
"toggle_record_pause": {
"limits": [
{
"counter": "toggle_record_pause_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} toggle_record_pause 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.
Free to start. No card required.
Toggles pause on the record output. Returns: Whether the output is paused after toggling. 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.
Register the OBS MCP Server MCP server in PolicyLayer and add a rule for toggle_record_pause: 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.
toggle_record_pause is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the toggle_record_pause 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.
Set action: deny in the PolicyLayer policy for toggle_record_pause. 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.
toggle_record_pause 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.
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.