uk-ea-flood-monitoring.warnings.current

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 50 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/uk-ea-flood-monitoring.warnings.current.md

WHAT IT DOES

What uk-ea-flood-monitoring.warnings.current does on Apibase

AI agents call uk-ea-flood-monitoring.warnings.current 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
`lat`	number	—	Latitude for a geographic radius filter — use with `long` and `dist`.
`dist`	number	—	Search radius in kilometres around `lat`/`long` — use with both.
`long`	number	—	Longitude for a geographic radius filter — use with `lat` and `dist`.
`county`	string	—	Filter by county name of the affected flood area (e.g. "Devon", "North Yorkshire").
`min_severity`	integer	—	Filter to warnings at this severity or more severe (lower number = more severe): 1=Severe Flood Warning (danger to life), 2=Flood Warning (immediate action), 3=

Parameters from the server's own tool schema.

RISK

Why uk-ea-flood-monitoring.warnings.current is rated Low

Retrieves public flood alert data from UK Environment Agency without side effects.

From the tool's definition Get currently active flood warnings and alerts, filterable by severity, county, or geographic radius

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs uk-ea-flood-monitoring.warnings.current 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 uk-ea-flood-monitoring.warnings.current, this is the rule to start with:

uk-ea-flood-monitoring.warnings.current Allowed

uk-ea-flood-monitoring.warnings.current is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "uk-ea-flood-monitoring.warnings.current": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every uk-ea-flood-monitoring.warnings.current call is checked against it from then on.

FAQ

Questions about uk-ea-flood-monitoring.warnings.current

What does the uk-ea-flood-monitoring.warnings.current tool do? +

Get currently active flood warnings and alerts for England from the UK Environment Agency, filterable by minimum severity (1=Severe Flood Warning down to 4=Warning no longer in force), county, or a geographic radius (lat/long/dist). Returns each warning's flood area, county, affected river or sea, severity, tidal flag, public message, and when it was raised/last changed. Data: environment.data.gov.uk/flood-monitoring, 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 uk-ea-flood-monitoring.warnings.current accept? +

uk-ea-flood-monitoring.warnings.current accepts 5 parameters: lat, dist, long, county, min_severity. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on uk-ea-flood-monitoring.warnings.current? +

Register the Apibase MCP server in PolicyLayer and add a rule for uk-ea-flood-monitoring.warnings.current: 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 uk-ea-flood-monitoring.warnings.current? +

uk-ea-flood-monitoring.warnings.current is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit uk-ea-flood-monitoring.warnings.current? +

Yes. Add a rate_limit block to the uk-ea-flood-monitoring.warnings.current 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 uk-ea-flood-monitoring.warnings.current completely? +

Set action: deny in the PolicyLayer policy for uk-ea-flood-monitoring.warnings.current. 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 uk-ea-flood-monitoring.warnings.current? +

uk-ea-flood-monitoring.warnings.current 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →