get_city_resource
Fetch ANY per-city data type by its key (generic accessor, 81 data types). One tool for the whole breadth of InfraNode: live data (air, traffic, transit stops, parking, charging, water-level, flood, sharing, fuel-prices, webcams, station-departures/-arrivals/stations, ...), statistics (demographi...
This record as markdown: /tools/dev-infranode-infranode/get-city-resource.md
What get_city_resource does on InfraNode
AI agents call get_city_resource 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 |
resource | string | Yes | Data type key to fetch, exactly as listed by get_city_overview / the infranode://catalog resource (the 'type' field), e.g. 'charging', 'parking', 'demographics' |
Parameters from the server's own tool schema.
Why get_city_resource is rated Low
Generic accessor retrieving public municipal data without modification, deletion, or execution capabilities.
From the tool's definition Fetch ANY per-city data, read-only MCP tools, open data
Attacks that exploit this kind of access
The rule that runs get_city_resource 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_resource, this is the rule to start with:
get_city_resource 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_resource call is checked against it from then on.
Questions about get_city_resource
Fetch ANY per-city data type by its key (generic accessor, 81 data types). One tool for the whole breadth of InfraNode: live data (air, traffic, transit stops, parking, charging, water-level, flood, sharing, fuel-prices, webcams, station-departures/-arrivals/stations, ...), statistics (demographics, unemployment, tourism, accidents, crime-stats, indicators, land-values, tax-rates, insolvencies, ...), multi-year TIME SERIES (sustainability: SDG indicators per municipality, one value per year from 2006 to 2023, so trends can be answered without stitching snapshots), infrastructure and environment (solar, solar-roofs, district-heating, energy, heritage, tree-cadastre, playgrounds, public-toilets, markets, education, ...) and more. Discover the valid keys and per-city coverage with get_city_overview(slug) or the infranode://catalog resource; the resource enum lists every key. Uncovered types return source_status="not_covered" (plus where they ARE available), never an error. Read-only. It is categorised as a Read tool in the InfraNode MCP Server, which means it retrieves data without modifying state.
get_city_resource accepts 2 parameters: slug, resource. Required: slug, resource. 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_resource: 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_resource 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_resource 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_resource. 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_resource 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