statbel.catalog.datasource_detail
Get full metadata (multilingual descriptions, supported locales, category, last data and metadata update timestamps) for one Statbel datasource, identified by the datasource_id from statbel.list_datasources. An invalid or unpublished id returns an empty upstream response. Data: bestat.statbel.fgo...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/statbel.catalog.datasource-detail.md
What statbel.catalog.datasource_detail does on Apibase
AI agents use statbel.catalog.datasource_detail to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
datasource_id | string | Yes | Datasource UUID from statbel.list_datasources (e.g. "e957ac31-44a2-4718-8469-10470d3c41d9"). An invalid or unpublished id returns an empty upstream response. |
Parameters from the server's own tool schema.
Why statbel.catalog.datasource_detail is rated Medium
An AI agent can call statbel.catalog.datasource_detail faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs statbel.catalog.datasource_detail 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 statbel.catalog.datasource_detail, this is the rule to start with:
statbel.catalog.datasource_detail stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 statbel.catalog.datasource_detail call is checked against it from then on.
Questions about statbel.catalog.datasource_detail
Get full metadata (multilingual descriptions, supported locales, category, last data and metadata update timestamps) for one Statbel datasource, identified by the datasource_id from statbel.list_datasources. An invalid or unpublished id returns an empty upstream response. Data: bestat.statbel.fgov.be, Belgian statistics office, no auth required. It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
statbel.catalog.datasource_detail accepts 1 parameter: datasource_id. Required: datasource_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 statbel.catalog.datasource_detail: 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.
statbel.catalog.datasource_detail is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the statbel.catalog.datasource_detail 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 statbel.catalog.datasource_detail. 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.
statbel.catalog.datasource_detail 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