start_burst · So Dsc MCP: Risk & Policy

WHAT IT DOES

What start_burst does on So Dsc

AI agents invoke start_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.

WHY IT NEEDS A POLICY

Why start_burst needs a policy

This tool remotely executes a camera action that produces observable external effects (photos capture). While not destructive or financial, it is an Execute-category tool because it triggers an external operation via the Camera Remote API. Severity is high because an AI agent could rapidly exhaust camera battery, fill storage, or take unwanted photos if the burst parameters are not carefully controlled.

From the tool's definition 'Start continuous (burst) shooting' — triggers physical camera hardware operation whose effects (photos taken, storage consumed, battery drained) depend on camera state and timing arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_burst Rate-limited

start_burst stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_burst": {
      "limits": [
        {
          "counter": "start_burst_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches So Dsc, so you can run agents against it safely.

FAQ

Questions about start_burst

What does the start_burst tool do? +

Start continuous (burst) shooting. Camera must already be in still. 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.

How do I enforce a policy on start_burst? +

Register the So Dsc MCP server in PolicyLayer and add a rule for start_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.

What risk level is start_burst? +

start_burst is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_burst? +

Yes. Add a rate_limit block to the start_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.

How do I block start_burst completely? +

Set action: deny in the PolicyLayer policy for start_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.

What MCP server provides start_burst? +

start_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.