rename_scene · Obs MCP: Risk & Policy

WHAT IT DOES

What rename_scene does on Obs

AI agents use rename_scene to create or update resources in Obs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obs environment.

WHY IT NEEDS A POLICY

Why rename_scene needs a policy

Renaming a scene modifies scene metadata but does not delete data or trigger external operations beyond OBS Studio's internal state changes. It is reversible (can be renamed again), making it Write rather than Destructive. The blast radius is medium because renaming scenes could break references in streaming/recording workflows if done maliciously, but the action is non-destructive and localized to OBS configuration.

From the tool's definition Tool name 'rename_scene' and description 'Rename an existing scene' indicate modification of existing data (scene metadata) in OBS Studio. This is a reversible change that alters configuration state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_scene Rate-limited

rename_scene stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_scene": {
      "limits": [
        {
          "counter": "rename_scene_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Obs, so you can run agents against it safely.

FAQ

Questions about rename_scene

What does the rename_scene tool do? +

Rename an existing scene. It is categorised as a Write tool in the Obs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_scene? +

Register the Obs MCP server in PolicyLayer and add a rule for rename_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. Nothing to install.

What risk level is rename_scene? +

rename_scene is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename_scene? +

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

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

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