Low Risk

obs-get-input-mute

Gets the audio mute state of an input

How to control obs-get-input-mute ↓

AI agents call obs-get-input-mute 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 only retrieves audio mute state information from OBS Studio. It performs no modifications, deletions, code execution, or financial operations. The action is purely informational and read-only, with no side effects or ability to affect OBS configuration or streaming state.

From the tool's definition Tool name 'obs-get-input-mute' and description 'Gets the audio mute state of an input' indicate a query operation that retrieves the current mute status without modifying any state.

Documented attack patterns abuse exactly the kind of access obs-get-input-mute 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-get-input-mute:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "obs-get-input-mute": {}
  }
}

obs-get-input-mute 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 obs-get-input-mute tool do? +

Gets the audio mute state of an input. 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 obs-get-input-mute? +

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

obs-get-input-mute is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit obs-get-input-mute? +

Yes. Add a rate_limit block to the obs-get-input-mute 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 obs-get-input-mute completely? +

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

obs-get-input-mute 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.