bundesbank-timeseries.reference.structure
Get the dimensions and valid codes for a Bundesbank dataflow (dataflow_id from bundesbank-timeseries.dataflows, e.g. "BBEX3" for exchange rates) in SDMX key position order, each with its code list (capped to 200 codes per dimension, with a total_codes count). Required to build the fully-specified...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/bundesbank-timeseries.reference.structure.md
What bundesbank-timeseries.reference.structure does on Apibase
AI agents call bundesbank-timeseries.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 |
|---|---|---|---|
dataflow_id | string | Yes | Bundesbank dataflow id, from bundesbank-timeseries.dataflows (e.g. "BBEX3" for exchange rates, "BBIN1" for central bank rates). Returns the dimension list (e.g. |
Parameters from the server's own tool schema.
Why bundesbank-timeseries.reference.structure is rated Low
Retrieves structural metadata from Bundesbank API; no side effects.
From the tool's definition Get the dimensions and valid codes for a Bundesbank dataflow
Attacks that exploit this kind of access
The rule that runs bundesbank-timeseries.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 bundesbank-timeseries.reference.structure, this is the rule to start with:
bundesbank-timeseries.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 bundesbank-timeseries.reference.structure call is checked against it from then on.
Questions about bundesbank-timeseries.reference.structure
Get the dimensions and valid codes for a Bundesbank dataflow (dataflow_id from bundesbank-timeseries.dataflows, e.g. "BBEX3" for exchange rates) in SDMX key position order, each with its code list (capped to 200 codes per dimension, with a total_codes count). Required to build the fully-specified "key" for bundesbank-timeseries.data. Data: api.statistiken.bundesbank.de (Bundesbank SDMX 2.1 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.
bundesbank-timeseries.reference.structure accepts 1 parameter: 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 bundesbank-timeseries.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.
bundesbank-timeseries.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 bundesbank-timeseries.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 bundesbank-timeseries.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.
bundesbank-timeseries.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