Low Risk

get_stream_status

Gets the status of the stream output. Returns: Dict containing stream status information including: - outputActive: Whether the output is active - outputReconnecting: Whether the output is reconnecting - outputTimecode: Timecode string of the output - outputDuration: Duration in milliseconds of t...

How to control get_stream_status ↓

AI agents call get_stream_status to retrieve information from OBS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and returns stream status information without modifying, executing operations, or triggering external actions. It is a read-only operation that retrieves current state data from OBS Studio. The blast radius of misuse is minimal—an AI agent could only observe streaming status, not control it or cause harm.

From the tool's definition Tool name 'get_stream_status' and description 'Gets the status of the stream output' with return values that are purely informational (outputActive, outputReconnecting, outputTimecode, outputDuration, outputBytes, outputSkippedFrames, outputTotalFrames)…

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_stream_status": {}
  }
}

get_stream_status is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_stream_status tool do? +

Gets the status of the stream output. Returns: Dict containing stream status information including: - outputActive: Whether the output is active - outputReconnecting: Whether the output is reconnecting - outputTimecode: Timecode string of the output - outputDuration: Duration in milliseconds of the output - outputBytes: Total bytes sent by the output - outputSkippedFrames: Number of frames skipped by the output - outputTotalFrames: Total frames processed by the output. It is categorised as a Read tool in the OBS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_stream_status? +

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

get_stream_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_stream_status? +

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

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

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