Gets the status of the record output. Returns: Dict containing record status information including: - outputActive: Whether the output is active - outputPaused: Whether the output is paused - outputTimecode: Timecode string of the output - outputDuration: Duration in milliseconds of the output - ...
AI agents call get_record_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 purely queries and returns existing record status data without creating, modifying, deleting, or executing any operations. It is a read-only operation with minimal security risk, as it only exposes metadata about an ongoing or past recording session.
From the tool's definition The tool 'get_record_status' retrieves status information about the record output, including outputActive, outputPaused, outputTimecode, outputDuration, outputBytes, and outputPath.
Documented attack patterns abuse exactly the kind of access get_record_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_record_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_record_status": {}
}
}get_record_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 record output. Returns: Dict containing record status information including: - outputActive: Whether the output is active - outputPaused: Whether the output is paused - outputTimecode: Timecode string of the output - outputDuration: Duration in milliseconds of the output - outputBytes: Total bytes recorded - outputPath: File path of the recording. 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_record_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_record_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_record_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_record_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_record_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.