get_site_details
AI agents call get_site_details 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.
The tool name 'get_' prefix is characteristic of read operations that retrieve information without modification. In the context of a lighting control system, retrieving site details is a non-destructive query operation. Confidence is moderate rather than high because the empty description prevents full confirmation, but the naming convention and sibling tools strongly suggest this is a read operation.
From the tool's definition Tool name 'get_site_details' indicates a retrieval operation. Description is empty, but sibling tools like 'get_device_health', 'get_live_light_levels', 'get_sensor_readings', 'get_system_variables', and 'list_*' all indicate read-only queries consistent with…
Attacks that exploit this kind of access
get_site_details. 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_site_details: 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_site_details 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_site_details 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_site_details. 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_site_details 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 →