ea-hydrology.readings.range
Get a date-ranged time series of readings (date, value, quality, completeness) for one EA hydrology data series, identified by the measure_id from ea-hydrology.station_measures. Requires min_date and max_date (YYYY-MM-DD, inclusive). Data: environment.data.gov.uk/hydrology, UK Open Government Lic...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ea-hydrology.readings.range.md
What ea-hydrology.readings.range does on Apibase
AI agents call ea-hydrology.readings.range to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max readings to return (default 500, max 2000). |
max_date | string | Yes | End date (inclusive), format YYYY-MM-DD. |
min_date | string | Yes | Start date (inclusive), format YYYY-MM-DD. |
measure_id | string | Yes | Measure identifier returned by ea-hydrology.station_measures. |
Parameters from the server's own tool schema.
Why ea-hydrology.readings.range is rated Low
Retrieves historical hydrology measurement data within specified date range with no side effects.
From the tool's definition Get a date-ranged time series of readings; no auth required; public government data
Attacks that exploit this kind of access
The rule that runs ea-hydrology.readings.range safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ea-hydrology.readings.range, this is the rule to start with:
ea-hydrology.readings.range is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every ea-hydrology.readings.range call is checked against it from then on.
Questions about ea-hydrology.readings.range
Get a date-ranged time series of readings (date, value, quality, completeness) for one EA hydrology data series, identified by the measure_id from ea-hydrology.station_measures. Requires min_date and max_date (YYYY-MM-DD, inclusive). Data: environment.data.gov.uk/hydrology, UK Open Government Licence v3.0, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ea-hydrology.readings.range accepts 4 parameters: limit, max_date, min_date, measure_id. Required: max_date, min_date, measure_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for ea-hydrology.readings.range: 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 Apibase. Nothing to install.
ea-hydrology.readings.range 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 ea-hydrology.readings.range 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 ea-hydrology.readings.range. 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.
ea-hydrology.readings.range is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue