brreg.registry.sub_units
List all registered sub-units (underenheter) for a Norwegian parent company — branches, departments, production sites, and physical locations. Each sub-unit has its own organisation number, name, org form, NACE industry code, municipality, and employee count. Useful for mapping a company's operat...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/brreg.registry.sub-units.md
What brreg.registry.sub_units does on Apibase
AI agents call brreg.registry.sub_units 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 |
|---|---|---|---|
page | integer | — | Zero-based page number for pagination (default 0). |
size | integer | — | Number of sub-units per page (1–50, default 10). |
org_number | string | Yes | Organisation number of the parent company (9 digits). Returns all registered sub-units (branches, departments, locations) that belong to this parent entity. |
Parameters from the server's own tool schema.
Why brreg.registry.sub_units is rated Low
Retrieves publicly registered company structural data without modification or side effects.
From the tool's definition List all registered sub-units, organisation number, name, industry code, municipality, employee count
Attacks that exploit this kind of access
The rule that runs brreg.registry.sub_units 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.sub_units, this is the rule to start with:
brreg.registry.sub_units 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.sub_units call is checked against it from then on.
Questions about brreg.registry.sub_units
List all registered sub-units (underenheter) for a Norwegian parent company — branches, departments, production sites, and physical locations. Each sub-unit has its own organisation number, name, org form, NACE industry code, municipality, and employee count. Useful for mapping a company's operational footprint across Norway. Large companies like Equinor or NHO can have hundreds of sub-units. Paginated (up to 50/page). 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.sub_units accepts 3 parameters: page, size, 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.sub_units: 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.sub_units 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.sub_units 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.sub_units. 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.sub_units 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