AI agents use set_moodlight to create or update resources in Ulanzi — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ulanzi environment.
The tool modifies the mood lighting state of a smart pixel clock, which is a reversible configuration change. It does not retrieve data (Read), execute arbitrary code (Execute), delete anything (Destructive), or involve financial transactions (Financial). It falls squarely into Write category as a state modification.
From the tool's definition Tool named 'set_moodlight' with description 'Set mood lighting on the clock' indicates a state modification operation on a smart device's lighting configuration. This is a reversible change to device settings.
Attacks that exploit this kind of access
Set mood lighting on the clock. It is categorised as a Write tool in the Ulanzi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ulanzi MCP server in PolicyLayer and add a rule for set_moodlight: 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 Ulanzi. Nothing to install.
set_moodlight 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_moodlight 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_moodlight. 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_moodlight is provided by the Ulanzi MCP server (jelloeater/ulanzi-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 →