get_city_overview
Get a ONE-CALL overview of everything InfraNode knows about a German city. Start here for any city question. Returns: the city's base data, a CATALOG of all 81 available data types (weather, air quality, public transit, trains, traffic, charging, parking, solar, energy, demographics, taxes, accid...
This record as markdown: /tools/dev-infranode-infranode/get-city-overview.md
What get_city_overview does on InfraNode
AI agents call get_city_overview 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | City identifier, e.g. 'berlin' or 'hamburg'. Resolved leniently: the German name with or without umlauts, any casing, a common English exonym or short form also |
Parameters from the server's own tool schema.
Why get_city_overview is rated Low
Tool retrieves city data and resource metadata with no side effects or modifications.
From the tool's definition ONE-CALL overview, Returns: the city's base data, a CATALOG, read-only
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_city_overview 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 get_city_overview, this is the rule to start with:
get_city_overview is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect InfraNode, apply this rule, and every get_city_overview call is checked against it from then on.
Questions about get_city_overview
Get a ONE-CALL overview of everything InfraNode knows about a German city. Start here for any city question. Returns: the city's base data, a CATALOG of all 81 available data types (weather, air quality, public transit, trains, traffic, charging, parking, solar, energy, demographics, taxes, accidents, tourism, heritage, trees, population density, playgrounds, post boxes and many more), each with its coverage status and the exact tool to call next (for most data types that is get_city_resource(slug, resource=<type>)), plus a small live highlights snapshot (current weather, air quality and train departures). Data types not yet covered for this city show where they ARE available so you can pivot. InfraNode keeps adding data and cities, so the catalog grows over time. Read-only. It is categorised as a Read tool in the InfraNode MCP Server, which means it retrieves data without modifying state.
get_city_overview accepts 1 parameter: slug. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the InfraNode MCP server in PolicyLayer and add a rule for get_city_overview: 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.
get_city_overview is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_city_overview 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.
Set action: deny in the PolicyLayer policy for get_city_overview. 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.
get_city_overview 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.
More on InfraNode, and thousands of servers like it.
This server
Across the catalogue