set_colour
AI agents use set_colour to create or update resources in Zencontrol Cloud — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zencontrol Cloud environment.
This tool creates or modifies lighting system state (color settings) reversibly. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). While empty description reduces confidence slightly, the name and context of a lighting control system clearly indicate Write category.
From the tool's definition Tool name 'set_colour' indicates modification of light color properties in a DALI-2 lighting control system. Sibling tools like 'control_light' and 'get_live_light_levels' confirm this is a control/write interface for physical lighting systems.
Attacks that exploit this kind of access
set_colour. It is categorised as a Write tool in the Zencontrol Cloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zencontrol Cloud MCP server in PolicyLayer and add a rule for set_colour: 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 Zencontrol Cloud. Nothing to install.
set_colour 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 set_colour 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 set_colour. 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.
set_colour is provided by the Zencontrol Cloud MCP server (owretch/zencontrol-cloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →