AI agents call baseline_list_zones to retrieve information from Baseline without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists configuration and status information about irrigation zones without creating, modifying, or deleting any data. It is a straightforward read operation with no side effects. Severity is low because zone configuration data is informational only and misuse would not cause operational harm to the irrigation system.
From the tool's definition Tool description states 'Zone configuration for a controller' with retrieval of status fields (number, name, decoder serial, enabled state, flow, agronomy details).
Attacks that exploit this kind of access
Zone configuration for a controller: number, name, decoder serial, enabled state, designed/learned flow, and hydrozone agronomy details. It is categorised as a Read tool in the Baseline MCP Server, which means it retrieves data without modifying state.
Register the Baseline MCP server in PolicyLayer and add a rule for baseline_list_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 Baseline. Nothing to install.
baseline_list_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 baseline_list_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 baseline_list_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.
baseline_list_zones is provided by the Baseline MCP server (swannman/baseline-irrigation-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 →