AI agents invoke obs-stop-output 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 executes a control command that stops OBS outputs (streaming/recording streams). It is not Read (no data retrieval), Write (not creating/modifying data reversibly), Destructive (stopping a stream doesn't delete data), or Financial. It is Execute because it triggers an external operation whose effects depend on which output is stopped.
From the tool's definition The tool 'obs-stop-output' stops an output, which terminates an active operation (likely streaming or recording). The description states it 'Stops an output' — this is an action that triggers external effects via the OBS WebSocket protocol.
Documented attack patterns abuse exactly the kind of access obs-stop-output 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 obs-stop-output:
{
"version": "1",
"default": "deny",
"tools": {
"obs-stop-output": {
"limits": [
{
"counter": "obs-stop-output_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} obs-stop-output 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.
Stops an 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.
Register the OBS MCP Server MCP server in PolicyLayer and add a rule for obs-stop-output: 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.
obs-stop-output 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 obs-stop-output 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 obs-stop-output. 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.
obs-stop-output 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.