hungary-ksh.reference.dataset_metadata
Get full metadata for one KSH dataset (dataset_id from hungary-ksh.dataset_search) — title, description, and the distribution list (distribution_id, format CSV/XML, download URL, temporal coverage, license) needed before calling hungary-ksh.dataset_data. Data: data.ksh.hu (KSH), no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/hungary-ksh.reference.dataset-metadata.md
What hungary-ksh.reference.dataset_metadata does on Apibase
AI agents call hungary-ksh.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 |
|---|---|---|---|
dataset_id | string | Yes | KSH dataset UUID, from hungary-ksh.dataset_search (e.g. "f44d314b-bc27-40a7-b34e-af01b3c4ab05" for Population). |
Parameters from the server's own tool schema.
Why hungary-ksh.reference.dataset_metadata is rated Low
Retrieves dataset metadata and distribution information without modifying data or triggering external operations.
From the tool's definition Get full metadata for one KSH dataset, no side effects
Attacks that exploit this kind of access
The rule that runs hungary-ksh.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 hungary-ksh.reference.dataset_metadata, this is the rule to start with:
hungary-ksh.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 hungary-ksh.reference.dataset_metadata call is checked against it from then on.
Questions about hungary-ksh.reference.dataset_metadata
Get full metadata for one KSH dataset (dataset_id from hungary-ksh.dataset_search) — title, description, and the distribution list (distribution_id, format CSV/XML, download URL, temporal coverage, license) needed before calling hungary-ksh.dataset_data. Data: data.ksh.hu (KSH), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
hungary-ksh.reference.dataset_metadata accepts 1 parameter: dataset_id. Required: dataset_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 hungary-ksh.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.
hungary-ksh.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 hungary-ksh.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 hungary-ksh.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.
hungary-ksh.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