New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

ea-hydrology.stations.search

Search the UK Environment Agency hydrology monitoring network for river, groundwater, and rainfall stations, filterable by river name, freetext label search, or what the station measures (waterFlow, waterLevel, rainfall, temperature, groundwaterLevel). Returns station_id, name, river/catchment, c...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 40 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ea-hydrology.stations.search.md

What ea-hydrology.stations.search does on Apibase

AI agents call ea-hydrology.stations.search 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.

ParameterTypeRequiredDescription
limit integer — Max stations to return (default 20, max 200).
search string — Freetext search matching the station label/name (e.g. "Farmoor").
river_name string — Filter stations by river name, partial match (e.g. "River Thames").
observed_property string — Filter stations by what they measure: waterFlow (river flow m3/s), waterLevel (river level), rainfall, temperature, or groundwaterLevel (borehole).

Parameters from the server's own tool schema.

Why ea-hydrology.stations.search is rated Low

Retrieves public hydrology station metadata and coordinates with no side effects or data modification.

From the tool's definition Search the UK Environment Agency hydrology monitoring network for river, groundwater, and rainfall stations

Questions about ea-hydrology.stations.search

What does the ea-hydrology.stations.search tool do? +

Search the UK Environment Agency hydrology monitoring network for river, groundwater, and rainfall stations, filterable by river name, freetext label search, or what the station measures (waterFlow, waterLevel, rainfall, temperature, groundwaterLevel). Returns station_id, name, river/catchment, coordinates, and measure count — use the station_id with ea-hydrology.station_measures to see its available data series. 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.

What parameters does ea-hydrology.stations.search accept? +

ea-hydrology.stations.search accepts 4 parameters: limit, search, river_name, observed_property. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ea-hydrology.stations.search? +

Register the Apibase MCP server in PolicyLayer and add a rule for ea-hydrology.stations.search: 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.

What risk level is ea-hydrology.stations.search? +

ea-hydrology.stations.search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ea-hydrology.stations.search? +

Yes. Add a rate_limit block to the ea-hydrology.stations.search 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.

How do I block ea-hydrology.stations.search completely? +

Set action: deny in the PolicyLayer policy for ea-hydrology.stations.search. 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.

What MCP server provides ea-hydrology.stations.search? +

ea-hydrology.stations.search 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.