turn_on_bulb · IntelliGlow MCP: Risk & Policy

WHAT IT DOES

What turn_on_bulb does on IntelliGlow

AI agents invoke turn_on_bulb to trigger actions in IntelliGlow. 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 turn_on_bulb needs a policy

Turning on a physical smart bulb is an external hardware operation with real-world side effects. The description is empty, so classification relies on the tool name and server context. Sibling tools like 'turn_off_bulb', 'set_bulb_brightness', and 'set_bulb_color' confirm this server performs direct hardware control. Execute is appropriate as it triggers an external operation (powering on a physical device).

From the tool's definition Tool name 'turn_on_bulb'; server description states it controls real smart bulbs via UDP network communication with direct hardware control

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

turn_on_bulb Rate-limited

turn_on_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": {
    "turn_on_bulb": {
      "limits": [
        {
          "counter": "turn_on_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 IntelliGlow, so you can run agents against it safely.

FAQ

Questions about turn_on_bulb

What does the turn_on_bulb tool do? +

turn_on_bulb. It is categorised as a Execute tool in the IntelliGlow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on turn_on_bulb? +

Register the IntelliGlow MCP server in PolicyLayer and add a rule for turn_on_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 IntelliGlow. Nothing to install.

What risk level is turn_on_bulb? +

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

Can I rate-limit turn_on_bulb? +

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

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

turn_on_bulb is provided by the IntelliGlow MCP server (shree-bd/intelliglow-ai-voice-mcp-iot-platform). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.