AI agents call baseline_list_controllers 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 performs a query operation that retrieves configuration and status data about irrigation controllers. It has no side effects, does not modify data, and does not execute external operations. The optional companyId parameter allows filtering but does not change the read-only nature.
From the tool's definition Tool description states it 'List[s] sites and controllers' and server description emphasizes 'read-only interaction'. The tool retrieves status information (model, firmware, subscription, device counts) without modifying or executing actions.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List sites and controllers (with model, firmware, subscription, device counts) across every organization the account can access. Pass companyId to limit to one org. 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_controllers: 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_controllers 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_controllers 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_controllers. 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_controllers 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 →