List all zones for a specific controller, with their numbers, names, and enabled state.
AI agents call get_zones to retrieve information from Home Controller without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward query operation that retrieves configuration metadata about zones in a smart home controller. It performs no writes, executions, deletions, or financial operations. The blast radius of misuse is minimal—an agent could only learn about available zones, which is informational only. Classified as Read with low severity.
From the tool's definition Tool name 'get_zones' and description 'List all zones for a specific controller' indicate a retrieval operation with no side effects. Returns enumerated data (numbers, names, enabled state) without modifying any state.
Attacks that exploit this kind of access
List all zones for a specific controller, with their numbers, names, and enabled state. It is categorised as a Read tool in the Home Controller MCP Server, which means it retrieves data without modifying state.
Register the Home Controller MCP server in PolicyLayer and add a rule for get_zones: 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 Home Controller. Nothing to install.
get_zones 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_zones 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_zones. 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_zones is provided by the Home Controller MCP server (winsthuang/home-controller). 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 →