Low Risk

get_cities

Get city catalog for lookups - raw location records with optional translations, coordinates, and countdown times

How to control get_cities ↓

What get_cities does on RedAlert MCP Server

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

Low Risk

Why get_cities needs a policy

This tool queries and returns a static catalog of city location records (with optional metadata like coordinates and translations). It performs a read-only lookup operation with no ability to modify, delete, or trigger external actions. The data retrieved is reference information used for location lookups. Severity is low as misuse would only expose geographic information already publicly available in the catalog.

From the tool's definition Tool name 'get_cities' and description 'Get city catalog for lookups - raw location records' indicate retrieval of reference data with no modification or side effects.

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

How to control get_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_cities:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_cities": {}
  }
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_cities

What does the get_cities tool do? +

Get city catalog for lookups - raw location records with optional translations, coordinates, and countdown times. 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_cities? +

Register the RedAlert MCP Server MCP server in PolicyLayer and add a rule for get_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_cities? +

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

Can I rate-limit get_cities? +

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

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

get_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.

Free to start. No card required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.