czso.reference.dataset_metadata

SERVERApibase SOURCEapibase-mcp-client

Medium RISK CLASS

Category Write

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/czso.reference.dataset-metadata.md

WHAT IT DOES

What czso.reference.dataset_metadata does on Apibase

AI agents use czso.reference.dataset_metadata to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.

Parameter	Type	Required	Description
`dataset_id`	string	Yes	CZSO dataset id, from czso.dataset_list (e.g. "130141r25" for 2024 population movement, "010022" for consumer price indices).

Parameters from the server's own tool schema.

RISK

Why czso.reference.dataset_metadata is rated Medium

An AI agent can call czso.reference.dataset_metadata faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs czso.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 czso.reference.dataset_metadata, this is the rule to start with:

czso.reference.dataset_metadata Rate-limited

czso.reference.dataset_metadata stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "czso.reference.dataset_metadata": {
      "limits": [
        {
          "counter": "czso.reference.dataset_metadata_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every czso.reference.dataset_metadata call is checked against it from then on.

FAQ

Questions about czso.reference.dataset_metadata

What does the czso.reference.dataset_metadata tool do? +

Get full metadata for one CZSO dataset (dataset_id from czso.dataset_list) — description, update frequency, temporal coverage, tags, and the resource list (download URL + format) needed before calling czso.dataset_data. Data: vdb.czso.cz (Czech Statistical Office open-data catalog), no auth required. It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does czso.reference.dataset_metadata accept? +

czso.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.

How do I enforce a policy on czso.reference.dataset_metadata? +

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

What risk level is czso.reference.dataset_metadata? +

czso.reference.dataset_metadata is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit czso.reference.dataset_metadata? +

Yes. Add a rate_limit block to the czso.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.

How do I block czso.reference.dataset_metadata completely? +

Set action: deny in the PolicyLayer policy for czso.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.

What MCP server provides czso.reference.dataset_metadata? +

czso.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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →