get_recent_alerts

Get list of recent disaster alerts from the last N hours.

Server Api https://api.gdacs.org/mcp
Category Read
Risk class Low
Parameters 20 required

What get_recent_alerts does on Api

AI agents call get_recent_alerts to retrieve information from Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
hours integer Number of hours to look back (default 24, max 168)
minAlertLevel string | null Minimum alert level: 'green', 'orange', or 'red'

Parameters from the server's own tool schema.

Why get_recent_alerts needs a policy

This tool retrieves or queries disaster alert information from www.gdacs.org without performing any side effects, modifications, or destructive operations. It is a straightforward data retrieval operation that belongs in the Read category. Severity is low because misuse would only result in accessing publicly available disaster information, with no blast radius for financial, operational, or data integrity impacts.

From the tool's definition Tool name 'get_recent_alerts' and description 'Get list of recent disaster alerts' indicate retrieval of existing data with no modification, deletion, or execution.

Questions about get_recent_alerts

What does the get_recent_alerts tool do? +

Get list of recent disaster alerts from the last N hours. It is categorised as a Read tool in the Api MCP Server, which means it retrieves data without modifying state.

What parameters does get_recent_alerts accept? +

get_recent_alerts accepts 2 parameters: hours, minAlertLevel. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_recent_alerts? +

Register the Api MCP server in PolicyLayer and add a rule for get_recent_alerts: 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 Api. Nothing to install.

What risk level is get_recent_alerts? +

get_recent_alerts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_recent_alerts? +

Yes. Add a rate_limit block to the get_recent_alerts 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 get_recent_alerts completely? +

Set action: deny in the PolicyLayer policy for get_recent_alerts. 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 get_recent_alerts? +

get_recent_alerts is provided by the Api MCP server (https://api.gdacs.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.