Low Risk

get_stats

Gets statistics about OBS, obs-websocket, and the current session. Returns: Dict containing various OBS statistics including CPU usage, memory usage, available disk space, and session information

How to control get_stats ↓

AI agents call get_stats 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 retrieves and queries system and session statistics from OBS Studio without modifying, deleting, or executing any operations. It is purely informational and has no destructive, financial, or code-execution capabilities. The blast radius of misuse is minimal—an agent could only access monitoring data about the streaming system.

From the tool's definition The tool description states it 'Gets statistics about OBS' and 'Returns: Dict containing various OBS statistics including CPU usage, memory usage, available disk space, and session information'.

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

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

get_stats 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_stats tool do? +

Gets statistics about OBS, obs-websocket, and the current session. Returns: Dict containing various OBS statistics including CPU usage, memory usage, available disk space, and session information. 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_stats? +

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

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

Can I rate-limit get_stats? +

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

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

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