AI agents call list_scenes to retrieve information from Obs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and enumerates existing scenes from OBS Studio without modifying, deleting, or executing any operations. It is a pure read operation that poses minimal security risk even if invoked by an AI agent, as it only exposes information about the current OBS configuration.
From the tool's definition Tool name is 'list_scenes' and description states 'List all scenes in OBS.' This is a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List all scenes in OBS. It is categorised as a Read tool in the Obs MCP Server, which means it retrieves data without modifying state.
Register the Obs MCP server in PolicyLayer and add a rule for list_scenes: 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. Nothing to install.
list_scenes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_scenes 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.
Set action: deny in the PolicyLayer policy for list_scenes. 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.
list_scenes is provided by the Obs MCP server (larscangit/obs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →