Sets the current scene transition. Args: transition_name: Name of the transition to set as current
AI agents use set_current_scene_transition to create or update resources in OBS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OBS MCP Server environment.
This tool modifies the active scene transition setting in OBS Studio. It changes a configuration value (which transition is currently active) without deleting data or executing arbitrary code. The change is reversible by setting a different transition. Blast radius is low as it only affects the visual transition effect between scenes.
From the tool's definition Sets the current scene transition
Documented attack patterns abuse exactly the kind of access set_current_scene_transition 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 set_current_scene_transition:
{
"version": "1",
"default": "deny",
"tools": {
"set_current_scene_transition": {
"limits": [
{
"counter": "set_current_scene_transition_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_current_scene_transition 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.
Free to start. No card required.
Sets the current scene transition. Args: transition_name: Name of the transition to set as current. It is categorised as a Write tool in the OBS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OBS MCP Server MCP server in PolicyLayer and add a rule for set_current_scene_transition: 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.
set_current_scene_transition is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_current_scene_transition 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 set_current_scene_transition. 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.
set_current_scene_transition 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.
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.