trigger_hotkey_by_name

THE RISK

High Risk

This tool triggers external actions through OBS hotkeys. The actual side effects are determined by the hotkey's configuration and could range from benign (scene switch) to severe (unexpected stream start/stop, source toggling affecting broadcast, or invoking external scripts). It performs code/action execution whose outcomes depend on arguments and are not immediately reversible in all cases.

From the tool's definition Tool 'trigger_hotkey_by_name' executes a hotkey action whose effects depend entirely on what that hotkey is configured to do in OBS Studio.

Documented attack patterns abuse exactly the kind of access trigger_hotkey_by_name gives an agent:

HOW TO CONTROL TRIGGER_HOTKEY_BY_NAME

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 trigger_hotkey_by_name:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "trigger_hotkey_by_name": {
      "limits": [
        {
          "counter": "trigger_hotkey_by_name_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

trigger_hotkey_by_name stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register OBS MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More OBS MCP Server tools

Destructive obs-remove-input Removes an existing input Destructive obs-remove-profile Removes a profile. If the current profile is chosen, it will change to a different profile Destructive obs-remove-scene Remove a scene from OBS Destructive obs-remove-scene-item Remove a scene item from a scene Destructive obs-remove-source-filter Removes a filter from a source Destructive remove_scene Removes a scene from OBS. Args: scene_name: Name of the scene to remove Destructive remove_scene_item Removes a scene item from a scene. Args: scene_name: Name of the scene th Execute obs-start-output Starts an output

All 200 OBS MCP Server tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in OBS MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the trigger_hotkey_by_name tool do? +

Triggers a hotkey using its name. Args: hotkey_name: Name of the hotkey to trigger. It is categorised as a Execute tool in the OBS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on trigger_hotkey_by_name? +

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

trigger_hotkey_by_name is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit trigger_hotkey_by_name? +

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

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

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

GOVERN OBS →

Free to start. No card required.

200 OBS MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT TRIGGER_HOTKEY_BY_NAME ON OBS MCP SERVER DOES

// THE RISK

// HOW TO CONTROL TRIGGER_HOTKEY_BY_NAME

// EXPLORE