AI agents call baseline_get_history 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 historical time-series data from an irrigation controller without modifying any state, creating side effects, or executing commands. It is purely a data retrieval operation consistent with the read-only nature of the baseline-mcp server. The low severity reflects minimal blast radius—misuse would only expose existing historical data.
From the tool's definition Tool name 'baseline_get_history' and description 'Modern reporting time-series for a single device' indicate data retrieval. Server description explicitly states 'read-only interaction' and 'historical reporting'.
Attacks that exploit this kind of access
Modern reporting time-series for a single device. Kinds:. 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_get_history: 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_get_history 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_get_history 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_get_history. 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_get_history 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 →