light_set
Turn on a light and optionally set brightness_pct and rgb_color.
This record as markdown: /tools/mcp-control-plane/light-set.md
What light_set does on Mcp Control Plane
AI agents use light_set to create or update resources in Mcp Control Plane, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Control Plane environment.
Why light_set is rated Medium
This tool modifies the state of a smart home light (via Home Assistant integration), setting it on and adjusting brightness/color. It is a reversible state change (the light can be turned off or reconfigured), placing it in the Write category. Misuse has minimal blast radius — it only affects lighting.
From the tool's definition Turn on a light and optionally set brightness_pct and rgb_color
Attacks that exploit this kind of access
The rule that runs light_set safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For light_set, this is the rule to start with:
light_set stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every light_set call is checked against it from then on.
Questions about light_set
Turn on a light and optionally set brightness_pct and rgb_color. It is categorised as a Write tool in the Mcp Control Plane MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for light_set: 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 Mcp Control Plane. Nothing to install.
light_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the light_set 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.
Set action: deny in the PolicyLayer policy for light_set. 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.
light_set is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
This server
Across the catalogue