set_bulb_brightness · IntelliGlow MCP: Risk & Policy

WHAT IT DOES

What set_bulb_brightness does on IntelliGlow

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

Setting bulb brightness triggers an external hardware operation via UDP, changing the physical state of a real device. This is an Execute-category action (triggering external operations). The description is empty, so confidence is reduced, but context from sibling tools (turn_on_bulb, turn_off_bulb, set_bulb_color) confirms this server controls physical hardware.

From the tool's definition Tool name 'set_bulb_brightness' on a server that 'control[s] real smart bulbs via UDP network communication' and performs 'direct hardware control'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_bulb_brightness Rate-limited

set_bulb_brightness 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": {
    "set_bulb_brightness": {
      "limits": [
        {
          "counter": "set_bulb_brightness_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 set_bulb_brightness

What does the set_bulb_brightness tool do? +

set_bulb_brightness. 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 set_bulb_brightness? +

Register the IntelliGlow MCP server in PolicyLayer and add a rule for set_bulb_brightness: 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 set_bulb_brightness? +

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

Can I rate-limit set_bulb_brightness? +

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

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

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