bundesbank-timeseries.reference.dataflows
Search or list Deutsche Bundesbank economic time-series dataflows — ~94 official series covering exchange rates, interest rates, money supply, prices, and balance of payments. Filter by name/id with query, or omit to list all. Use the returned dataflow_id with bundesbank-timeseries.structure and ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/bundesbank-timeseries.reference.dataflows.md
What bundesbank-timeseries.reference.dataflows does on Apibase
AI agents call bundesbank-timeseries.reference.dataflows 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 |
|---|---|---|---|
query | string | — | Filter dataflows by name or id substring, case-insensitive (e.g. "exchange rate", "interest", "BBEX3"). Omit to list all ~94 available dataflows. |
Parameters from the server's own tool schema.
Why bundesbank-timeseries.reference.dataflows is rated Low
Retrieves public economic metadata; no side effects, modifications, or code execution.
From the tool's definition Search or list Deutsche Bundesbank economic time-series dataflows; no auth required.
Attacks that exploit this kind of access
The rule that runs bundesbank-timeseries.reference.dataflows 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.dataflows, this is the rule to start with:
bundesbank-timeseries.reference.dataflows 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.dataflows call is checked against it from then on.
Questions about bundesbank-timeseries.reference.dataflows
Search or list Deutsche Bundesbank economic time-series dataflows — ~94 official series covering exchange rates, interest rates, money supply, prices, and balance of payments. Filter by name/id with query, or omit to list all. Use the returned dataflow_id with bundesbank-timeseries.structure and 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.dataflows accepts 1 parameter: query. 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.dataflows: 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.dataflows 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.dataflows 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.dataflows. 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.dataflows 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