dbnomics.data.datasets
List all datasets published by a specific statistical agency on DBnomics. For example: provider WB has WDI (World Development Indicators, 396K+ series); provider OECD has QNA (quarterly national accounts), KEI, MEI, and 200+ more; provider IMF has WEO, BOP, IFS; Eurostat has 1,000+ datasets. Retu...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/dbnomics.data.datasets.md
What dbnomics.data.datasets does on Apibase
AI agents call dbnomics.data.datasets 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 | — | Number of datasets to return (1–200, default 50) |
offset | integer | — | Pagination offset — number of datasets to skip (default 0) |
provider_code | string | Yes | DBnomics provider code (e.g. WB for World Bank, OECD, IMF, Eurostat, ECB). Use dbnomics.providers to list valid codes. |
Parameters from the server's own tool schema.
Why dbnomics.data.datasets is rated Low
Tool retrieves public statistical metadata with no side effects or data modification capability.
From the tool's definition List all datasets published by a specific statistical agency; open data under CC-BY 4.0
Attacks that exploit this kind of access
The rule that runs dbnomics.data.datasets 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 dbnomics.data.datasets, this is the rule to start with:
dbnomics.data.datasets 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 dbnomics.data.datasets call is checked against it from then on.
Questions about dbnomics.data.datasets
List all datasets published by a specific statistical agency on DBnomics. For example: provider WB has WDI (World Development Indicators, 396K+ series); provider OECD has QNA (quarterly national accounts), KEI, MEI, and 200+ more; provider IMF has WEO, BOP, IFS; Eurostat has 1,000+ datasets. Returns dataset codes, names, and series counts. Use the returned dataset codes with dbnomics.data.series to browse available time series. First call dbnomics.data.providers to get valid provider codes. No API key required — open data under CC-BY 4.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
dbnomics.data.datasets accepts 3 parameters: limit, offset, provider_code. Required: provider_code. 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 dbnomics.data.datasets: 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.
dbnomics.data.datasets 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 dbnomics.data.datasets 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 dbnomics.data.datasets. 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.
dbnomics.data.datasets 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