compare
Compare ONE resource across MULTIPLE cities in a single response. Fans the resource out over the listed cities and returns a per-city source_status (ok/disabled/no_data/error/not_found), so a missing or failing city source does not spoil the whole answer. Read-only.
This record as markdown: /tools/dev-infranode-infranode/compare.md
What compare does on InfraNode
AI agents call compare 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 |
|---|---|---|---|
cities | string | Yes | Comma-separated list of city slugs, e.g. 'berlin,koeln,hamburg' (max. 28 cities). |
resource | string | Yes | Resource to compare. Supported: 'weather' (DWD), 'air' (UBA air quality), 'indicators' (INKAR socioeconomic indicators incl. unemployment rate and EV charging c |
Parameters from the server's own tool schema.
Why compare is rated Low
This tool retrieves and queries data across multiple cities for comparison purposes. The explicit 'Read-only' designation, combined with the action of comparing resources and returning source status without modifying data, places this firmly in the Read category. The minimal blast radius (comparison of open city data) warrants low severity.
From the tool's definition Tool description explicitly states 'Read-only' and describes comparing a resource across multiple cities, returning status information from multiple sources. No creation, modification, deletion, code execution, or financial operations are performed.
Attacks that exploit this kind of access
The rule that runs compare 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 compare, this is the rule to start with:
compare 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 compare call is checked against it from then on.
Questions about compare
Compare ONE resource across MULTIPLE cities in a single response. Fans the resource out over the listed cities and returns a per-city source_status (ok/disabled/no_data/error/not_found), so a missing or failing city source does not spoil the whole answer. Read-only. It is categorised as a Read tool in the InfraNode MCP Server, which means it retrieves data without modifying state.
compare accepts 2 parameters: cities, resource. Required: cities, 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 compare: 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.
compare 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 compare 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 compare. 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.
compare 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