stop_bulb · So Dsc MCP: Risk & Policy

WHAT IT DOES

What stop_bulb does on So Dsc

AI agents invoke stop_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 stop_bulb needs a policy

This tool executes a command to a remote camera device that produces a physical side effect (shutter closure). While not destructive to data and not financial, it is an Execute-class action because it triggers external operations on hardware. The severity is medium: misuse could waste photos or interrupt legitimate shooting, but cannot corrupt data or cause financial loss.

From the tool's definition 'Close the bulb shutter' — directly controls camera hardware (shutter mechanism), triggering an external physical operation whose effects depend on the camera state and timing arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_bulb Rate-limited

stop_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": {
    "stop_bulb": {
      "limits": [
        {
          "counter": "stop_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 stop_bulb

What does the stop_bulb tool do? +

Close the bulb shutter. 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 stop_bulb? +

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

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

Can I rate-limit stop_bulb? +

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

Set action: deny in the PolicyLayer policy for stop_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 stop_bulb? +

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