Low Risk

get_entity_roles

Get all roles for a specific entity

How to control get_entity_roles ↓

What get_entity_roles does on Norwegian Business Registry MCP Server

AI agents call get_entity_roles to retrieve information from Norwegian Business Registry MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_entity_roles needs a policy

This tool retrieves organizational role information from the Norwegian Business Registry. It performs a read-only query operation with no side effects—it does not create, modify, delete, execute code, or trigger external actions. The data returned (roles associated with an entity) is business registry metadata that is already public.

From the tool's definition Tool name 'get_entity_roles' and description 'Get all roles for a specific entity' indicate a retrieval operation that queries existing data about entity roles without modification, deletion, or execution of code.

Documented attack patterns abuse exactly the kind of access get_entity_roles gives an agent:

How to control get_entity_roles

PolicyLayer is an MCP gateway — it sits between your AI agents and Norwegian Business Registry MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_entity_roles:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_entity_roles": {}
  }
}

get_entity_roles is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Norwegian Business Registry MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_entity_roles

What does the get_entity_roles tool do? +

Get all roles for a specific entity. It is categorised as a Read tool in the Norwegian Business Registry MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_entity_roles? +

Register the Norwegian Business Registry MCP Server MCP server in PolicyLayer and add a rule for get_entity_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 Norwegian Business Registry MCP Server. Nothing to install.

What risk level is get_entity_roles? +

get_entity_roles is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_entity_roles? +

Yes. Add a rate_limit block to the get_entity_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.

How do I block get_entity_roles completely? +

Set action: deny in the PolicyLayer policy for get_entity_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.

What MCP server provides get_entity_roles? +

get_entity_roles is provided by the Norwegian Business Registry MCP Server MCP server (reidar80/brreg-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Norwegian Business Registry MCP Server tool call.

Start from Norwegian Business Registry MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

15 Norwegian Business Registry MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.