AI agents use obs-set-current-profile 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 state of OBS Studio by switching the current profile. It is a configuration change that is reversible (you can switch back), making it a Write operation. Misuse could disrupt streaming/recording setups by changing active profile unexpectedly, hence medium severity.
From the tool's definition Switches to a profile
Documented attack patterns abuse exactly the kind of access obs-set-current-profile 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 obs-set-current-profile:
{
"version": "1",
"default": "deny",
"tools": {
"obs-set-current-profile": {
"limits": [
{
"counter": "obs-set-current-profile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}obs-set-current-profile 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.
Switches to a profile. 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 obs-set-current-profile: 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.
obs-set-current-profile 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 obs-set-current-profile 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 obs-set-current-profile. 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.
obs-set-current-profile 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.