list_cities

List all covered cities (slug, federal state, population, coverage). Takes no arguments. Call this first to discover valid city slugs before invoking any city-scoped tool. Read-only.

SERVERInfraNode SOURCEhttps://mcp.infranode.dev/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/dev-infranode-infranode/list-cities.md

WHAT IT DOES

What list_cities does on InfraNode

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

RISK

Why list_cities is rated Low

This tool retrieves and queries data without modification, deletion, or execution of external operations. It is a pure read operation used for data discovery, fitting clearly into the Read category with minimal security risk.

From the tool's definition Tool description explicitly states 'Read-only' and performs listing operation ('List all covered cities') with no arguments and no side effects. Returns metadata (slug, federal state, population, coverage) for discovery purposes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_cities safely

PolicyLayer is an MCP gateway: it sits between your AI agents and InfraNode, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_cities, this is the rule to start with:

list_cities Allowed

list_cities is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect InfraNode, apply this rule, and every list_cities call is checked against it from then on.

FAQ

Questions about list_cities

What does the list_cities tool do? +

List all covered cities (slug, federal state, population, coverage). Takes no arguments. Call this first to discover valid city slugs before invoking any city-scoped tool. Read-only. It is categorised as a Read tool in the InfraNode MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_cities? +

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

What risk level is list_cities? +

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

Can I rate-limit list_cities? +

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

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

list_cities is provided by the InfraNode MCP server (https://mcp.infranode.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on InfraNode, and thousands of servers like it.

This server

All 12 InfraNode tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →