Get information about a specific Norwegian municipality
AI agents call get_municipality 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.
This tool retrieves public municipality information from the Norwegian Business Registry without creating, modifying, deleting, or executing any operations. It is a straightforward query operation that returns publicly available data, posing minimal risk of misuse.
From the tool's definition Tool name 'get_municipality' and description 'Get information about a specific Norwegian municipality' indicate a simple data retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_municipality gives an agent:
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_municipality:
{
"version": "1",
"default": "deny",
"tools": {
"get_municipality": {}
}
} get_municipality is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get information about a specific Norwegian municipality. It is categorised as a Read tool in the Norwegian Business Registry MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Norwegian Business Registry MCP Server MCP server in PolicyLayer and add a rule for get_municipality: 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.
get_municipality 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 get_municipality 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 get_municipality. 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.
get_municipality 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.
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.