slovakia-statistics.reference.dataset_metadata
Get the dimensions and valid value codes for one DATAcube table (cube_code from slovakia-statistics.dataset_search) — every dimension (e.g. year, region, indicator, sex) with its full list of selectable codes and labels, needed to build the "selections" object for slovakia-statistics.dataset_data...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/slovakia-statistics.reference.dataset-metadata.md
What slovakia-statistics.reference.dataset_metadata does on Apibase
AI agents call slovakia-statistics.reference.dataset_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 |
|---|---|---|---|
cube_code | string | Yes | Table code from slovakia-statistics.dataset_search (e.g. "as1001rs" for "Population and attributes of age"). |
Parameters from the server's own tool schema.
Why slovakia-statistics.reference.dataset_metadata is rated Low
Tool only retrieves metadata about dataset dimensions; no side effects.
From the tool's definition Get the dimensions and valid value codes for one DATAcube table
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs slovakia-statistics.reference.dataset_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 slovakia-statistics.reference.dataset_metadata, this is the rule to start with:
slovakia-statistics.reference.dataset_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 slovakia-statistics.reference.dataset_metadata call is checked against it from then on.
Questions about slovakia-statistics.reference.dataset_metadata
Get the dimensions and valid value codes for one DATAcube table (cube_code from slovakia-statistics.dataset_search) — every dimension (e.g. year, region, indicator, sex) with its full list of selectable codes and labels, needed to build the "selections" object for slovakia-statistics.dataset_data. Data: data.statistics.sk, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
slovakia-statistics.reference.dataset_metadata accepts 1 parameter: cube_code. Required: cube_code. 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 slovakia-statistics.reference.dataset_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.
slovakia-statistics.reference.dataset_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 slovakia-statistics.reference.dataset_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 slovakia-statistics.reference.dataset_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.
slovakia-statistics.reference.dataset_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