start_bulb · So Dsc MCP: Risk & Policy

WHAT IT DOES

What start_bulb does on So Dsc

AI agents invoke start_bulb 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_bulb needs a policy

The tool executes a real-world physical action (opening the camera shutter) that affects the external environment. This is an Execute category tool because it triggers an external operation that cannot be easily reversed and whose outcome depends on context (lighting, subject, duration). While not strictly irreversible (the shutter can be closed via 'stop_bulb'), it commits the camera to a specific physical action.

From the tool's definition Tool is called 'start_bulb' and described as 'Open the shutter for bulb exposure.' This directly triggers a camera action—opening the shutter—which is an external operation whose effects depend on camera state and context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_bulb Rate-limited

start_bulb 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_bulb": {
      "limits": [
        {
          "counter": "start_bulb_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_bulb

What does the start_bulb tool do? +

Open the shutter for bulb exposure. Camera must be in Manual. 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_bulb? +

Register the So Dsc MCP server in PolicyLayer and add a rule for start_bulb: 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_bulb? +

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

Can I rate-limit start_bulb? +

Yes. Add a rate_limit block to the start_bulb 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_bulb completely? +

Set action: deny in the PolicyLayer policy for start_bulb. 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_bulb? +

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