get_stats_cities

THE RISK

Low Risk

Why get_stats_cities needs a policy

This tool retrieves and queries historical or aggregated alert statistics at the city level. It performs no data modification, deletion, code execution, or financial operations. The pagination and search parameters are filters for retrieving existing data. This is a straightforward Read category tool with minimal risk if misused—worst case being excessive queries or information disclosure of public alert statistics.

From the tool's definition Tool name 'get_stats_cities' and description 'Get city-level alert statistics with pagination, search, and optional translations/coordinates' indicate a data retrieval operation only.

Documented attack patterns abuse exactly the kind of access get_stats_cities gives an agent:

POLICY

How to control get_stats_cities

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_stats_cities": {}
  }
}

get_stats_cities is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register RedAlert MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More RedAlert MCP Server tools

Execute subscribe_alerts Connect to RedAlert Socket.IO server and start receiving real-time emergency alerts. Optio Write unsubscribe_alerts Disconnect from RedAlert Socket.IO server and stop receiving real-time alerts. Clears the Read get_active_alerts Get real-time snapshot of cities currently under alert, grouped by alert type (missiles, e Read get_alert_subscription_status Check the current real-time alert subscription status including connection state, subscrib Read get_cities Get city catalog for lookups - raw location records with optional translations, coordinate Read get_stats_distribution Get alert distribution grouped by category or origin, with filtering, sorting, and paginat Read get_stats_history Get detailed historical alert records with full city data, filtering, sorting, and paginat Read get_stats_summary Get high-level overview of the alert system: totals, unique cities/zones, and optional top

All 12 RedAlert MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_stats_cities

What does the get_stats_cities tool do? +

Get city-level alert statistics with pagination, search, and optional translations/coordinates. It is categorised as a Read tool in the RedAlert MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_stats_cities? +

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

What risk level is get_stats_cities? +

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

Can I rate-limit get_stats_cities? +

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

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

get_stats_cities is provided by the RedAlert MCP Server MCP server (ozba/redalert-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every RedAlert MCP Server tool call.

Start from RedAlert MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →