New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

ssbnorway.stats.population

Get Norwegian population statistics from the official SSB population register (table 07459). Returns total resident population by year as a JSON-stat2 dataset. Covers Norway as a whole (region_code="0") or any county/municipality by region code. Data goes back to 1986 and is updated annually (ref...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 20 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ssbnorway.stats.population.md

What ssbnorway.stats.population does on Apibase

AI agents call ssbnorway.stats.population 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.

ParameterTypeRequiredDescription
years integer — Number of most recent years to include (1–20, default 5). Table 07459 covers 1986 to the current reference year.
region_code string — Norwegian region code from SSB classification. "0" = The whole country (default). County codes (2024 structure): "31" Østfold, "32" Akershus, "03" Oslo, "33" Bu

Parameters from the server's own tool schema.

Why ssbnorway.stats.population is rated Low

Retrieves public demographic data with no side effects or modification capabilities.

From the tool's definition Get Norwegian population statistics, Returns total resident population, query official register

Questions about ssbnorway.stats.population

What does the ssbnorway.stats.population tool do? +

Get Norwegian population statistics from the official SSB population register (table 07459). Returns total resident population by year as a JSON-stat2 dataset. Covers Norway as a whole (region_code="0") or any county/municipality by region code. Data goes back to 1986 and is updated annually (reference date January 1st each year). Region codes: "0" = whole country, "03" = Oslo, "11" = Rogaland, "15" = Møre og Romsdal, "18" = Nordland, "46" = Vestland, "50" = Trøndelag. Use ssbnorway.data.metadata on table 07459 to get all 994 municipality-level region codes. This is a simplified shortcut — for sex/age breakdowns use ssbnorway.data.query with table 07459 and the Kjonn/Alder dimension codes from ssbnorway.data.metadata. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does ssbnorway.stats.population accept? +

ssbnorway.stats.population accepts 2 parameters: years, region_code. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ssbnorway.stats.population? +

Register the Apibase MCP server in PolicyLayer and add a rule for ssbnorway.stats.population: 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.

What risk level is ssbnorway.stats.population? +

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

Can I rate-limit ssbnorway.stats.population? +

Yes. Add a rate_limit block to the ssbnorway.stats.population 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 ssbnorway.stats.population completely? +

Set action: deny in the PolicyLayer policy for ssbnorway.stats.population. 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 ssbnorway.stats.population? +

ssbnorway.stats.population 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.