# hent_hoyde

Hent terrenghøyde (meter over havet) for et koordinat fra Kartverkets høydedata-API. Bruker DTM 1m der det finnes.

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

## Facts

- Tool: `hent_hoyde`
- 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": "hent_hoyde",
    "arguments": {}
  }
}
```

## Why hent_hoyde is rated Low

This tool retrieves elevation data for a given geographic coordinate. It is a pure read operation that queries Norwegian geographic data without side effects, state changes, or ability to modify underlying data. The blast radius of misuse is minimal—an agent could retrieve elevation data for any coordinate, but cannot alter, delete, or execute operations.

From the tool's own definition: "Tool name 'hent_hoyde' (fetch elevation) and description 'Hent terrenghøyde (meter over havet) for et koordinat' (fetch terrain elevation in meters above sea level for a coordinate) indicate data retrieval only."

## Use case

AI agents call hent_hoyde 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": {
    "hent_hoyde": {}
  }
}
```

## Other tools on Kartverket (6)

- `sok_adresse` — Read — https://policylayer.com/tools/3121n-nor-data-kartverket-mcp/sok-adresse.md
- `sok_bygning` — Read — https://policylayer.com/tools/3121n-nor-data-kartverket-mcp/sok-bygning.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