// SCAN REPORT

RedAlert MCP Server

12 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

2 can modify or destroy data

10 read-only

12 tools total

Community server · catalogue entry verified 12/06/2026

How to control RedAlert MCP Server ↓

TOOL MAP

What RedAlert MCP Server exposes to your agents

Read (10) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous RedAlert MCP Server tools

Execute · Medium subscribe_alerts This tool initiates an external network connection to a Socket.IO server and establishes a persistent subscription/stream. Write · Medium unsubscribe_alerts This tool terminates a subscription/connection and clears buffered data.

2 of RedAlert MCP Server's 12 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control RedAlert MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and RedAlert MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "unsubscribe_alerts": {
    "limits": [
      {
        "counter": "unsubscribe_alerts_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_active_alerts": {
    "limits": [
      {
        "counter": "get_active_alerts_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register RedAlert MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON REDALERT →

Free to start. No card required.

FULL CATALOGUE

All 12 RedAlert MCP Server tools

EXECUTE 1 tools

Execute subscribe_alerts Connect to RedAlert Socket.IO server and start receiving real-time emergency alerts. Optionally filter by aler

WRITE 1 tools

Write unsubscribe_alerts Disconnect from RedAlert Socket.IO server and stop receiving real-time alerts. Clears the alert buffer.

READ 10 tools

Read get_active_alerts Get real-time snapshot of cities currently under alert, grouped by alert type (missiles, earthquakes, etc.) Read get_alert_subscription_status Check the current real-time alert subscription status including connection state, subscribed types, and buffer Read get_cities Get city catalog for lookups - raw location records with optional translations, coordinates, and countdown tim Read get_stats_cities Get city-level alert statistics with pagination, search, and optional translations/coordinates Read get_stats_distribution Get alert distribution grouped by category or origin, with filtering, sorting, and pagination Read get_stats_history Get detailed historical alert records with full city data, filtering, sorting, and pagination Read get_stats_summary Get high-level overview of the alert system: totals, unique cities/zones, and optional top cities/zones/origin Read health_check Check the health status of the RedAlert API Read poll_alerts Retrieve buffered real-time alerts that arrived since the last poll. Must call subscribe_alerts first. Read search_shelters Find nearby shelters. Provide lat/lon directly, or just a city name to auto-resolve coordinates.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about RedAlert MCP Server

How do I prevent bulk modifications through RedAlert MCP Server? +

The RedAlert MCP Server server has 1 write tools including unsubscribe_alerts. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach RedAlert MCP Server.

How many tools does the RedAlert MCP Server MCP server expose? +

12 tools across 2 categories: Execute, Read. 10 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on RedAlert MCP Server? +

Register the RedAlert MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every RedAlert MCP Server tool call.

Deterministic rules across all 12 RedAlert MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON REDALERT →

Free to start. No card required.

12 RedAlert MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.