AI agents invoke set_sleep to trigger actions in Ulanzi. 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.
This tool triggers an external physical operation on the Ulanzi TC001 Smart Pixel Clock device, putting it into deep sleep mode. While reversible in theory (the device can be woken up), it executes a real-world hardware state change with operational consequences.
From the tool's definition Send the clock to deep sleep mode
Attacks that exploit this kind of access
Send the clock to deep sleep mode. It is categorised as a Execute tool in the Ulanzi MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ulanzi MCP server in PolicyLayer and add a rule for set_sleep: 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_sleep is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the set_sleep 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_sleep. 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_sleep 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 →