brreg.registry.search
Search Norway's official business registry (Brønnøysundregistrene) for companies and organisations. Filter by company name, municipality (4-digit code), organisation form (AS/ASA/ENK/NUF etc.), or NACE industry code. Returns organisation number, name, org form, VAT status, employee count, address...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/brreg.registry.search.md
What brreg.registry.search does on Apibase
AI agents call brreg.registry.search 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 |
|---|---|---|---|
name | string | — | Company name or partial name to search (e.g. "Equinor", "Telenor", "DNB"). Case-insensitive. At least one filter (name, municipality_number, org_form, nace_code |
page | integer | — | Zero-based page number for pagination (default 0). |
size | integer | — | Number of results per page (1–20, default 5). |
org_form | string | — | Organization form code to filter by. Common values: AS=Private Limited Company, ASA=Public Limited Company, ENK=Sole Proprietorship, NUF=Foreign Entity Norwegia |
nace_code | string | — | NACE industry code to filter by (e.g. "06.100" for Extraction of crude oil, "47.110" for Retail in non-specialised stores, "62.010" for Computer programming). M |
municipality_number | string | — | Norwegian municipality number (4-digit code, e.g. "0301" for Oslo, "1103" for Stavanger). Restricts results to companies registered in that municipality. |
Parameters from the server's own tool schema.
Why brreg.registry.search is rated Low
Tool queries public business registry data with no side effects or write capabilities.
From the tool's definition Search Norway's official business registry for companies and organisations. Returns organisation number, name, org form, VAT status, employee count, address, primary NACE industry code.
Attacks that exploit this kind of access
The rule that runs brreg.registry.search 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.search, this is the rule to start with:
brreg.registry.search 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.search call is checked against it from then on.
Questions about brreg.registry.search
Search Norway's official business registry (Brønnøysundregistrene) for companies and organisations. Filter by company name, municipality (4-digit code), organisation form (AS/ASA/ENK/NUF etc.), or NACE industry code. Returns organisation number, name, org form, VAT status, employee count, address, primary NACE industry code, and bankruptcy/winding-up flags. Over 1 million entities registered. Data is NLOD 2.0 (commercial use permitted). No API key required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
brreg.registry.search accepts 6 parameters: name, page, size, org_form, nace_code, municipality_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.search: 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.search 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.search 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.search. 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.search 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