# sok_bygning

Finn bygninger (Matrikkelen-Bygningspunkt, Kartverket) rundt et koordinat (WGS84). Returnerer bygningstype (NS-3457, dekodet), bygningsstatus (dekodet — RA/IG indikerer byggeaktivitet), SEFRAK-minne (proxy for eldre bygg, hovedsakelig før 1900), kulturminne-flagg og avstand fra punktet. NB: byggeår finnes IKKE i det åpne datasettet (krever full Matrikkel-avtale) — SEFRAK-flagget er nærmeste åpne alderssignal. Kilde: Kartverket WFS, CC BY 4.0, avtale-fri.

Agent View of the PolicyLayer registry record for `sok_bygning`. HTML page: https://policylayer.com/tools/3121n-nor-data-kartverket-mcp/sok-bygning

## Facts

- Tool: `sok_bygning`
- Server: Kartverket (`@nor-data/kartverket-mcp`) — https://policylayer.com/tools/3121n-nor-data-kartverket-mcp.md
- Install: `npx -y @nor-data/kartverket-mcp`
- Homepage: https://github.com/3121n/nor-data-kartverket-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "sok_bygning",
    "arguments": {}
  }
}
```

## Why sok_bygning is rated Low

This tool retrieves and queries geographic building data from Kartverket's open API based on coordinates. It is purely a read operation that returns structured data about buildings (type, status, cultural heritage flags, distance) with no side effects. The tool requires only input coordinates (WGS84) and returns informational attributes. No data is created, modified, deleted, or used to trigger external actions.

From the tool's own definition: "Tool name 'sok_bygning' means 'search building'; description states it 'Finn bygninger' (find buildings) and 'Returnerer' (returns) building data like type, status, and historical flags around a coordinate."

## Use case

AI agents call sok_bygning to retrieve information from Kartverket without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Kartverket:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "sok_bygning": {}
  }
}
```

## Other tools on Kartverket (6)

- `hent_hoyde` — Read — https://policylayer.com/tools/3121n-nor-data-kartverket-mcp/hent-hoyde.md
- `sok_adresse` — Read — https://policylayer.com/tools/3121n-nor-data-kartverket-mcp/sok-adresse.md
- `sok_eiendom` — Read — https://policylayer.com/tools/3121n-nor-data-kartverket-mcp/sok-eiendom.md
- `sok_grunnkrets` — Read — https://policylayer.com/tools/3121n-nor-data-kartverket-mcp/sok-grunnkrets.md
- `sok_kommune` — Read — https://policylayer.com/tools/3121n-nor-data-kartverket-mcp/sok-kommune.md
- `sok_stedsnavn` — Read — https://policylayer.com/tools/3121n-nor-data-kartverket-mcp/sok-stedsnavn.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=3121n-nor-data-kartverket-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/3121n-nor-data-kartverket-mcp