AI agents invoke stop_burst to trigger actions in So Dsc. 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 a command that interrupts an in-flight camera operation (burst shooting). While not destructive—burst photos are preserved—it does control external hardware behavior and interrupt a running process. This is Execute rather than Write because it triggers an action on a remote device whose effect (stopping vs continuing burst) depends on timing and current state.
From the tool's definition Tool name 'stop_burst' stops an ongoing burst shooting operation on a remote camera. The description indicates it terminates an active camera action and returns postview URLs as a result.
Attacks that exploit this kind of access
Stop a running burst. Returns the list of postview URLs (one per. It is categorised as a Execute tool in the So Dsc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the So Dsc MCP server in PolicyLayer and add a rule for stop_burst: 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 So Dsc. Nothing to install.
stop_burst 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 stop_burst 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 stop_burst. 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.
stop_burst is provided by the So Dsc MCP server (nananek/so-dsc). 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 →