Gets the status of the replay buffer output. Returns: Dict containing: - outputActive: Whether the output is active
AI agents call get_replay_buffer_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.
This tool retrieves the current status of the replay buffer in OBS Studio. It performs a read-only query operation with no side effects—it does not create, modify, delete, or execute any actions. The low severity reflects minimal blast radius; misuse would only expose buffer status information without enabling unauthorized control of recording or streaming infrastructure.
From the tool's definition Tool name contains 'get_' prefix and description states it 'Gets the status of the replay buffer output' and 'Returns' information about outputActive status without modifying any state.
Documented attack patterns abuse exactly the kind of access get_replay_buffer_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_replay_buffer_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_replay_buffer_status": {}
}
}get_replay_buffer_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Gets the status of the replay buffer output. Returns: Dict containing: - outputActive: Whether the output is active. It is categorised as a Read tool in the OBS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OBS MCP Server MCP server in PolicyLayer and add a rule for get_replay_buffer_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.
get_replay_buffer_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_replay_buffer_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.
Set action: deny in the PolicyLayer policy for get_replay_buffer_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.
get_replay_buffer_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.
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.