Removes a profile. If the current profile is chosen, it will change to a different profile first
AI agents call obs-remove-profile to permanently remove resources in OBS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Profile removal is a destructive action that cannot be undone through the tool itself. While not as critical as deleting streaming content, removing configuration profiles could impact OBS workflows and require manual reconfiguration. This fits the Destructive category (irreversibly deletes data) rather than Write (which is reversible).
From the tool's definition Tool name contains 'remove' and description states 'Removes a profile' - this is an irreversible deletion operation. The description indicates it manages state by switching to a different profile if needed, but the core action is permanent removal.
Documented attack patterns abuse exactly the kind of access obs-remove-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-remove-profile:
{
"version": "1",
"default": "deny",
"hide": [
"obs-remove-profile"
]
} obs-remove-profile disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Removes a profile. If the current profile is chosen, it will change to a different profile first. It is categorised as a Destructive tool in the OBS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OBS MCP Server MCP server in PolicyLayer and add a rule for obs-remove-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-remove-profile is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the obs-remove-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-remove-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-remove-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.