sepa-scotland.rainfall.stations
Search Scotland's ~280-gauge live rainfall telemetry network by station name substring (e.g. "Glasgow"), or list all stations. Returns each station's number, name, latitude/longitude, and latest reading (value in mm and timestamp). Call sepa-scotland.station_current or sepa-scotland.rainfall_hist...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/sepa-scotland.rainfall.stations.md
What sepa-scotland.rainfall.stations does on Apibase
AI agents call sepa-scotland.rainfall.stations 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 | — | Maximum number of stations to return (1-50, default 20) |
query | string | — | Substring to match against rainfall gauge station names (e.g. "Glasgow"). Omit to list all ~280 stations. |
Parameters from the server's own tool schema.
Why sepa-scotland.rainfall.stations is rated Low
Retrieves public rainfall telemetry data with no side effects or modification capability.
From the tool's definition Search stations, list all stations, returns readings, no auth required
Attacks that exploit this kind of access
The rule that runs sepa-scotland.rainfall.stations 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 sepa-scotland.rainfall.stations, this is the rule to start with:
sepa-scotland.rainfall.stations 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 sepa-scotland.rainfall.stations call is checked against it from then on.
Questions about sepa-scotland.rainfall.stations
Search Scotland's ~280-gauge live rainfall telemetry network by station name substring (e.g. "Glasgow"), or list all stations. Returns each station's number, name, latitude/longitude, and latest reading (value in mm and timestamp). Call sepa-scotland.station_current or sepa-scotland.rainfall_history with a result's station_no for live or historical data. Data: SEPA (Scottish Environment Protection Agency), no auth required, Open Government Licence v3.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
sepa-scotland.rainfall.stations accepts 2 parameters: limit, query. 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 sepa-scotland.rainfall.stations: 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.
sepa-scotland.rainfall.stations 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 sepa-scotland.rainfall.stations 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 sepa-scotland.rainfall.stations. 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.
sepa-scotland.rainfall.stations 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