list_device_locations
AI agents call list_device_locations 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 retrieves and enumerates device location data without side effects. It fits the 'Read' category as a data query operation. Severity is low because location data exposure has limited blast radius compared to control operations (which this server also provides via 'control_light').
From the tool's definition Tool name 'list_device_locations' indicates retrieval of location data from devices. The empty description limits evidence specificity, but the 'list' prefix and context within a lighting control system (alongside tools like 'list_devices',…
Attacks that exploit this kind of access
list_device_locations. 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_device_locations: 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_device_locations 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_device_locations 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_device_locations. 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_device_locations 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 →