get_live_light_levels
AI agents call get_live_light_levels to retrieve information from Zencontrol Cloud without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries live light level data from a DALI-2 lighting system. No side effects or state changes occur—it only retrieves operational telemetry. Confidence is slightly reduced (0.85 vs 0.95) due to the empty description, which prevents direct confirmation of its scope and return data, but the naming convention and server context strongly indicate a read-only monitoring function.
From the tool's definition Tool name 'get_live_light_levels' indicates a retrieval operation. The naming pattern 'get_' is consistent with other read-only tools on the server (get_device_health, get_scope, get_sensor_readings, get_site_details, get_system_variables).
Attacks that exploit this kind of access
get_live_light_levels. It is categorised as a Read tool in the Zencontrol Cloud MCP Server, which means it retrieves data without modifying state.
Register the Zencontrol Cloud MCP server in PolicyLayer and add a rule for get_live_light_levels: 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.
get_live_light_levels is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_live_light_levels 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 get_live_light_levels. 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.
get_live_light_levels 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 →