norway-kartverket-stedsnavn.places.get_place
Get the full record for a single Norwegian place by its stedsnummer id (from search_names or search_by_point results). Returns all written name forms (incl. Sámi/minority-language forms where applicable), status, type, county, municipality, coordinates, last-updated date, and boundary geometry wh...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/norway-kartverket-stedsnavn.places.get-place.md
What norway-kartverket-stedsnavn.places.get_place does on Apibase
AI agents call norway-kartverket-stedsnavn.places.get_place 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 |
|---|---|---|---|
place_id | object | Yes | Norwegian place id (stedsnummer) to look up, e.g. 307915 for Oslo — from search_names or search_by_point results |
Parameters from the server's own tool schema.
Why norway-kartverket-stedsnavn.places.get_place is rated Low
Retrieves geographical data about Norwegian places with no side effects, write, or execution capabilities.
From the tool's definition Get the full record for a single Norwegian place by its stedsnummer id, Returns all written name forms, coordinates, boundary geometry
Attacks that exploit this kind of access
The rule that runs norway-kartverket-stedsnavn.places.get_place 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.get_place, this is the rule to start with:
norway-kartverket-stedsnavn.places.get_place 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.get_place call is checked against it from then on.
Questions about norway-kartverket-stedsnavn.places.get_place
Get the full record for a single Norwegian place by its stedsnummer id (from search_names or search_by_point results). Returns all written name forms (incl. Sámi/minority-language forms where applicable), status, type, county, municipality, coordinates, last-updated date, and boundary geometry where available. 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.get_place accepts 1 parameter: place_id. Required: place_id. 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.get_place: 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.get_place 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.get_place 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.get_place. 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.get_place 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