brreg.registry.entity
Retrieve full details for a specific Norwegian company or organisation by its 9-digit organisation number. Returns: name, organisation form, website, phone, email, employee count, registration date, founding date, VAT registration, bankruptcy/winding-up status, up to 3 NACE industry codes, munici...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/brreg.registry.entity.md
What brreg.registry.entity does on Apibase
AI agents call brreg.registry.entity 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 |
|---|---|---|---|
org_number | string | Yes | Norwegian organisation number — exactly 9 digits (e.g. "923609016" for Equinor, "982463718" for DNB). No spaces or dashes. |
Parameters from the server's own tool schema.
Why brreg.registry.entity is rated Low
Queries public business registry data without modifying, deleting, or executing operations.
From the tool's definition Retrieve full details for a specific Norwegian company by organisation number.
Attacks that exploit this kind of access
The rule that runs brreg.registry.entity 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 brreg.registry.entity, this is the rule to start with:
brreg.registry.entity 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 brreg.registry.entity call is checked against it from then on.
Questions about brreg.registry.entity
Retrieve full details for a specific Norwegian company or organisation by its 9-digit organisation number. Returns: name, organisation form, website, phone, email, employee count, registration date, founding date, VAT registration, bankruptcy/winding-up status, up to 3 NACE industry codes, municipality, postal address, business address, last annual report year, and parent entity. Ideal for KYB (Know Your Business) verification of Norwegian entities. Source: Brønnøysundregistrene, NLOD 2.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
brreg.registry.entity accepts 1 parameter: org_number. Required: org_number. 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 brreg.registry.entity: 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.
brreg.registry.entity 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 brreg.registry.entity 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 brreg.registry.entity. 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.
brreg.registry.entity 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