brreg.registry.roles
Retrieve statutory management roles for a Norwegian company — board of directors (STYR), CEO/daily manager (DAGL), auditor (REVI), chairman (LEDE), deputy members, signature rights, and other registered positions. Each role entry includes the person's first/last name, birth year, whether the role...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/brreg.registry.roles.md
What brreg.registry.roles does on Apibase
AI agents call brreg.registry.roles 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 | Organisation number of the company to retrieve roles for (9 digits). Returns all registered role groups including board of directors (STYR), CEO (DAGL), auditor |
Parameters from the server's own tool schema.
Why brreg.registry.roles is rated Low
Tool only retrieves and queries existing company registry data with no side effects.
From the tool's definition Retrieve statutory management roles, corporate governance checks, no write or delete operations
Attacks that exploit this kind of access
The rule that runs brreg.registry.roles 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.roles, this is the rule to start with:
brreg.registry.roles 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.roles call is checked against it from then on.
Questions about brreg.registry.roles
Retrieve statutory management roles for a Norwegian company — board of directors (STYR), CEO/daily manager (DAGL), auditor (REVI), chairman (LEDE), deputy members, signature rights, and other registered positions. Each role entry includes the person's first/last name, birth year, whether the role is still active, and (for corporate roles) the linked entity's org number and name. Essential for due diligence, UBO (Ultimate Beneficial Owner) research, and corporate governance checks. 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.roles 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.roles: 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.roles 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.roles 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.roles. 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.roles 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