list_scenes
AI agents call list_scenes 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 appears to list available lighting scenes, which is fundamentally a read operation that retrieves configuration or state data without modifying system state. There is no evidence of destructive, financial, or code execution capabilities. Confidence is slightly reduced due to the empty description, but the tool name and sibling operations provide sufficient context to classify with reasonable confidence.
From the tool's definition Tool name 'list_scenes' indicates retrieval of scene data. The description is empty, but the naming convention and context within a lighting control system (alongside other read operations like 'list_devices', 'get_device_health', 'get_live_light_levels')…
Attacks that exploit this kind of access
list_scenes. 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 list_scenes: 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.
list_scenes 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 list_scenes 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 list_scenes. 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.
list_scenes 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 →