norway-kartverket-stedsnavn.places.search_by_point
Find Norwegian place names near a geographic coordinate (reverse geocoding), from the Kartverket Stedsnavn register. Returns matching place ids, types, names, municipality, and coordinates within the given radius. Data: Kartverket (Norwegian Mapping Authority), NLOD 2.0 open licence, no auth requ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/norway-kartverket-stedsnavn.places.search-by-point.md
What norway-kartverket-stedsnavn.places.search_by_point does on Apibase
AI agents call norway-kartverket-stedsnavn.places.search_by_point to retrieve information from Apibase 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 |
|---|---|---|---|
lat | number | Yes | Decimal degree latitude (WGS84/EUREF89) within Norway, e.g. 59.91273 for Oslo |
lng | number | Yes | Decimal degree longitude (WGS84/EUREF89) within Norway, e.g. 10.74609 for Oslo |
limit | integer | — | Maximum place names to return (default 10, max 30) |
radius_m | number | — | Search radius in metres around lat/lng (default 500, max 10000) |
Parameters from the server's own tool schema.
Why norway-kartverket-stedsnavn.places.search_by_point is rated Low
Retrieves publicly available geographic data without modification, deletion, or external state changes.
From the tool's definition Find Norwegian place names near a geographic coordinate (reverse geocoding). Returns matching place ids, types, names, municipality, and coordinates.
Attacks that exploit this kind of access
The rule that runs norway-kartverket-stedsnavn.places.search_by_point safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For norway-kartverket-stedsnavn.places.search_by_point, this is the rule to start with:
norway-kartverket-stedsnavn.places.search_by_point 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 Apibase, apply this rule, and every norway-kartverket-stedsnavn.places.search_by_point call is checked against it from then on.
Questions about norway-kartverket-stedsnavn.places.search_by_point
Find Norwegian place names near a geographic coordinate (reverse geocoding), from the Kartverket Stedsnavn register. Returns matching place ids, types, names, municipality, and coordinates within the given radius. Data: Kartverket (Norwegian Mapping Authority), NLOD 2.0 open licence, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
norway-kartverket-stedsnavn.places.search_by_point accepts 4 parameters: lat, lng, limit, radius_m. Required: lat, lng. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for norway-kartverket-stedsnavn.places.search_by_point: 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 Apibase. Nothing to install.
norway-kartverket-stedsnavn.places.search_by_point 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 norway-kartverket-stedsnavn.places.search_by_point 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 norway-kartverket-stedsnavn.places.search_by_point. 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.
norway-kartverket-stedsnavn.places.search_by_point is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue