Get detailed info for a single Rachio zone.
AI agents call get_zone 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 tool queries information about a Rachio irrigation zone (likely a smart home watering system). It retrieves data without modifying state, executing code, deleting resources, or moving money. The blast radius of misuse is minimal—an attacker could only learn details about zone configuration, which poses minimal harm. Severity is low because reading zone metadata carries negligible risk.
From the tool's definition Tool name 'get_zone' and description 'Get detailed info for a single Rachio zone' indicate a retrieval operation with no modification or side effects. The verb 'Get' and the focus on retrieving 'detailed info' are characteristic of Read operations.
Attacks that exploit this kind of access
Get detailed info for a single Rachio zone. 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_zone: 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_zone 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_zone 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_zone. 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_zone 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 →