statistik-austria.series.dataset_data
Fetch rows from a Statistik Austria dataset's CSV data file (dataset_id from statistik-austria.dataset_search). Column codes are opaque (e.g. "C-STAATS-0", "F-VESTE_AM") — use statistik-austria.dataset_metadata for column meanings and statistik-austria.category_codes to decode category values (e....
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/statistik-austria.series.dataset-data.md
What statistik-austria.series.dataset_data does on Apibase
AI agents call statistik-austria.series.dataset_data 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 |
|---|---|---|---|
limit | integer | — | Max rows to return (1-200, default 20). |
offset | integer | — | Number of rows to skip, for paging through a large dataset. |
dataset_id | string | Yes | Statistik Austria dataset id, from statistik-austria.dataset_search (e.g. "OGD_konjunkturmonitor_KonMon_1"). |
Parameters from the server's own tool schema.
Why statistik-austria.series.dataset_data is rated Low
Tool retrieves public statistical data with no side effects or modifications possible.
From the tool's definition Fetch rows from a Statistik Austria dataset's CSV data file
Attacks that exploit this kind of access
The rule that runs statistik-austria.series.dataset_data 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 statistik-austria.series.dataset_data, this is the rule to start with:
statistik-austria.series.dataset_data 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 statistik-austria.series.dataset_data call is checked against it from then on.
Questions about statistik-austria.series.dataset_data
Fetch rows from a Statistik Austria dataset's CSV data file (dataset_id from statistik-austria.dataset_search). Column codes are opaque (e.g. "C-STAATS-0", "F-VESTE_AM") — use statistik-austria.dataset_metadata for column meanings and statistik-austria.category_codes to decode category values (e.g. "STAATS-9"). Rows capped 1-200 (default 20). Data: data.statistik.gv.at (Statistik Austria), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
statistik-austria.series.dataset_data accepts 3 parameters: limit, offset, 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 statistik-austria.series.dataset_data: 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.
statistik-austria.series.dataset_data 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 statistik-austria.series.dataset_data 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 statistik-austria.series.dataset_data. 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.
statistik-austria.series.dataset_data 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