statistics-denmark.data.table_info
Get the full metadata for a specific Statistics Denmark table — dimension codes, valid value codes, and human-readable labels needed to construct a data query. Returns table title, description, unit, last-updated timestamp, and an array of variables (dimensions) each with its code (e.g. "OMRÅDE" ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/statistics-denmark.data.table-info.md
What statistics-denmark.data.table_info does on Apibase
AI agents call statistics-denmark.data.table_info 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 | StatBank table ID (short alphanumeric code). Obtain from statistics-denmark.tables. Common tables: "FOLK1A" (population by region/sex/age/marital status, quarte |
Parameters from the server's own tool schema.
Why statistics-denmark.data.table_info is rated Low
Retrieves table metadata and schema information without modifying or executing queries.
From the tool's definition Get full metadata, dimension codes, valid value codes, human-readable labels
Attacks that exploit this kind of access
The rule that runs statistics-denmark.data.table_info 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 statistics-denmark.data.table_info, this is the rule to start with:
statistics-denmark.data.table_info 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 statistics-denmark.data.table_info call is checked against it from then on.
Questions about statistics-denmark.data.table_info
Get the full metadata for a specific Statistics Denmark table — dimension codes, valid value codes, and human-readable labels needed to construct a data query. Returns table title, description, unit, last-updated timestamp, and an array of variables (dimensions) each with its code (e.g. "OMRÅDE" for region), readable name, and the list of valid value codes with labels. This is the required second step before querying data: call statistics-denmark.data.tables to find a table ID, then statistics-denmark.data.table_info to learn the dimension codes and valid values, then statistics-denmark.data.query to retrieve actual data. Common table IDs: "FOLK1A" (quarterly population by region/sex/age/marital status), "BEFOLK1" (annual population by sex/age since 1971), "AKU1" (labour force survey), "NAN1" (GDP and national accounts), "PRIS111" (consumer price index). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
statistics-denmark.data.table_info 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 statistics-denmark.data.table_info: 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.
statistics-denmark.data.table_info 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 statistics-denmark.data.table_info 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 statistics-denmark.data.table_info. 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.
statistics-denmark.data.table_info 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