get_city
Get base data for a German city (population, area, coordinates). Sourced from Wikidata. Read-only. Useful as a first lookup to confirm a city exists and get its core attributes. For a broader question about the city (what data is available at all) use get_city_overview instead.
This record as markdown: /tools/dev-infranode-infranode/get-city.md
What get_city does on InfraNode
AI agents call get_city 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 is rated Low
This tool performs a simple data lookup operation on open public data from Wikidata. It returns immutable city attributes and cannot modify, delete, or execute any operations. The read-only designation, combined with the straightforward retrieval of static city information, makes this a low-risk Read operation.
From the tool's definition Tool description explicitly states 'Read-only' and retrieves 'base data for a German city (population, area, coordinates)' with 'no side effects'. Name 'get_city' and actions like 'lookup' and 'get' confirm data retrieval without modification.
Attacks that exploit this kind of access
The rule that runs get_city 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, this is the rule to start with:
get_city 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 call is checked against it from then on.
Questions about get_city
Get base data for a German city (population, area, coordinates). Sourced from Wikidata. Read-only. Useful as a first lookup to confirm a city exists and get its core attributes. For a broader question about the city (what data is available at all) use get_city_overview instead. It is categorised as a Read tool in the InfraNode MCP Server, which means it retrieves data without modifying state.
get_city 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: 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 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 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. 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 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