Low Risk

get_scene_item_locked

Gets the locked state of a scene item. Args: scene_name: Name of the scene the item is in scene_item_id: ID of the scene item Returns: Whether the scene item is locked

How to control get_scene_item_locked ↓

AI agents call get_scene_item_locked 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 queries the locked state of a scene item without causing any side effects, modifications, or external operations. It is purely informational and cannot alter OBS state, making it a Read category risk with low severity.

From the tool's definition Tool name is 'get_scene_item_locked' and description states it 'Gets the locked state of a scene item', returning 'Whether the scene item is locked'. The verb 'Get' and return-only operation with no modification capability indicate a retrieval action.

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

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

get_scene_item_locked 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_scene_item_locked tool do? +

Gets the locked state of a scene item. Args: scene_name: Name of the scene the item is in scene_item_id: ID of the scene item Returns: Whether the scene item is locked. 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_scene_item_locked? +

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

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

Can I rate-limit get_scene_item_locked? +

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

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

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