AI agents invoke start_streaming to trigger actions in Obs. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an external operation (streaming to a configured service) whose effects depend on OBS configuration and cannot be easily undone once live. While not destructive or financial, it is Execute-class because it runs an operation with significant real-world side effects (going live, broadcasting to an audience).
From the tool's definition Tool name 'start_streaming' and description 'Start OBS streaming' indicate execution of a streaming operation that triggers external network activity and public broadcast of media content.
Attacks that exploit this kind of access
Start OBS streaming. It is categorised as a Execute tool in the Obs MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Obs MCP server in PolicyLayer and add a rule for start_streaming: 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.
start_streaming is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_streaming 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 start_streaming. 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.
start_streaming 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 →