Get active flood warnings for England. Can filter by postcode or area.
AI agents call get_flood_warnings to retrieve information from GovUK MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a government data source to retrieve flood warning information. It has no side effects, does not modify any data, and does not trigger external operations. The worst-case misuse (e.g., scraping all flood warnings repeatedly) would be inefficient but not harmful. It is a straightforward Read operation with low blast radius.
From the tool's definition The tool description states 'Get active flood warnings for England' — it retrieves and queries existing data (active flood warnings) without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get active flood warnings for England. Can filter by postcode or area. It is categorised as a Read tool in the GovUK MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GovUK MCP Server MCP server in PolicyLayer and add a rule for get_flood_warnings: 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 GovUK MCP Server. Nothing to install.
get_flood_warnings 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 get_flood_warnings 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 get_flood_warnings. 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.
get_flood_warnings is provided by the GovUK MCP Server MCP server (stealth-labs-ltd/govuk-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 →