istat.reference.structure
Get the dimensions and valid codes for an ISTAT dataflow (dataflow_id from istat.dataflows, e.g. "101_1015_DF_DCSP_COLTIVAZIONI_1" for crop areas and production) — frequency, territory, and measure dimensions each with their code list (capped to 200 codes per dimension, with a total_codes count)....
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/istat.reference.structure.md
What istat.reference.structure does on Apibase
AI agents call istat.reference.structure 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 |
|---|---|---|---|
version | string | — | Dataflow version, from istat.dataflows (e.g. "1.0"). Omit to use the latest version. |
dataflow_id | string | Yes | ISTAT dataflow id, from istat.dataflows (e.g. "101_1015_DF_DCSP_COLTIVAZIONI_1" for crop areas and production). Returns the dimension list (e.g. FREQ, REF_AREA, |
Parameters from the server's own tool schema.
Why istat.reference.structure is rated Low
Retrieves metadata about dataflow dimensions; no data modification or side effects.
From the tool's definition Get the dimensions and valid codes for an ISTAT dataflow
Attacks that exploit this kind of access
The rule that runs istat.reference.structure 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 istat.reference.structure, this is the rule to start with:
istat.reference.structure 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 istat.reference.structure call is checked against it from then on.
Questions about istat.reference.structure
Get the dimensions and valid codes for an ISTAT dataflow (dataflow_id from istat.dataflows, e.g. "101_1015_DF_DCSP_COLTIVAZIONI_1" for crop areas and production) — frequency, territory, and measure dimensions each with their code list (capped to 200 codes per dimension, with a total_codes count). Use this to interpret the dimension labels returned by istat.data, or to build a narrower key filter. Data: esploradati.istat.it (ISTAT SDMX public REST API), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
istat.reference.structure accepts 2 parameters: version, dataflow_id. Required: dataflow_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 istat.reference.structure: 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.
istat.reference.structure 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 istat.reference.structure 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 istat.reference.structure. 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.
istat.reference.structure 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