Low Risk

get_current_preview_scene

Gets the current preview scene (only available when studio mode is enabled). Returns: Name of the current preview scene

How to control get_current_preview_scene ↓

AI agents call get_current_preview_scene 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 is a simple query operation that retrieves information about OBS Studio's current preview scene state. It performs no modifications, does not execute code or commands, does not delete data, and does not involve financial transactions. The tool has minimal blast radius—an agent calling it repeatedly or at unexpected times cannot cause harm beyond potentially high API load.

From the tool's definition Tool name 'get_current_preview_scene' and description 'Gets the current preview scene' indicate a retrieval operation with no side effects. Returns only the name of the current preview scene without modifying any state.

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

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

get_current_preview_scene 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_current_preview_scene tool do? +

Gets the current preview scene (only available when studio mode is enabled). Returns: Name of the current preview scene. 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_current_preview_scene? +

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

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

Can I rate-limit get_current_preview_scene? +

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

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

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