pois
Get points of interest in a German city, filtered by type. Sourced from OpenStreetMap. Read-only.
This record as markdown: /tools/dev-infranode-infranode/pois.md
What pois does on InfraNode
AI agents call pois 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 |
type | string | Yes | POI type from the API allowlist, one of: hospital, school, pharmacy, restaurant, police, kindergarten. |
Parameters from the server's own tool schema.
Why pois is rated Low
This tool queries and retrieves geographic/location data (points of interest filtered by type) from OpenStreetMap without creating, modifying, or deleting any data. It has no side effects and presents minimal security risk—typical of public geographic data queries.
From the tool's definition Tool description explicitly states 'Read-only' and the function retrieves 'points of interest' data with no modification capability. The MCP server is described as providing '12 lean read-only MCP tools'.
Attacks that exploit this kind of access
The rule that runs pois 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 pois, this is the rule to start with:
pois 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 pois call is checked against it from then on.
Questions about pois
Get points of interest in a German city, filtered by type. Sourced from OpenStreetMap. Read-only. It is categorised as a Read tool in the InfraNode MCP Server, which means it retrieves data without modifying state.
pois accepts 2 parameters: slug, type. Required: slug, type. 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 pois: 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.
pois 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 pois 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 pois. 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.
pois 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