ssbnorway.data.metadata
Get the full metadata for a specific SSB table — dimension codes, valid value codes, and human-readable labels needed to construct a data query. Returns table title, last-updated timestamp, and an array of variables (dimensions) each with its code (e.g. "Region"), readable name, list of valid val...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ssbnorway.data.metadata.md
What ssbnorway.data.metadata does on Apibase
AI agents call ssbnorway.data.metadata 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 |
|---|---|---|---|
table_id | string | Yes | SSB table ID (numeric string). Obtain from ssbnorway.search results. Common tables: "07459" (population by region/sex/age/year), "09842" (GDP per capita by year |
Parameters from the server's own tool schema.
Why ssbnorway.data.metadata is rated Low
Retrieves metadata and structure information only; enables queries but performs no data access or side effects.
From the tool's definition Get metadata, dimension codes, valid value codes, human-readable labels, returns table structure information.
Attacks that exploit this kind of access
The rule that runs ssbnorway.data.metadata 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 ssbnorway.data.metadata, this is the rule to start with:
ssbnorway.data.metadata 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 ssbnorway.data.metadata call is checked against it from then on.
Questions about ssbnorway.data.metadata
Get the full metadata for a specific SSB table — dimension codes, valid value codes, and human-readable labels needed to construct a data query. Returns table title, last-updated timestamp, and an array of variables (dimensions) each with its code (e.g. "Region"), readable name, list of valid value codes, and corresponding labels. This is the required second step before querying data: call ssbnorway.data.search to find a table ID, then ssbnorway.data.metadata to learn the dimension codes and valid values, then ssbnorway.data.query to retrieve actual data. Common table IDs: "07459" (population by region/sex/age/year), "09842" (GDP per capita), "05111" (labour force), "03013" (CPI). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ssbnorway.data.metadata accepts 1 parameter: table_id. Required: table_id. 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 ssbnorway.data.metadata: 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.
ssbnorway.data.metadata 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 ssbnorway.data.metadata 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 ssbnorway.data.metadata. 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.
ssbnorway.data.metadata 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