statbel.catalog.list_views
Browse the Statbel beSTAT catalog of ~1300 curated, ready-to-query views (cross-tabs of Belgian official statistics), filterable by locale (fr/nl/de/en) and a case-insensitive name search. Each view exists as a separate record per language. Returns view_id, name, locale, and the backing data_sour...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/statbel.catalog.list-views.md
What statbel.catalog.list_views does on Apibase
AI agents call statbel.catalog.list_views 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 | — | Max number of results to return (1-100). Defaults to 20. |
locale | string | — | Language of the catalog to browse: "fr" (French, default), "nl" (Dutch), "de" (German), or "en" (English). Each view exists as a separate record per locale. |
offset | integer | — | Number of results to skip, for pagination. Defaults to 0. |
search | string | — | Case-insensitive substring filter on the view name (e.g. "population density"). |
Parameters from the server's own tool schema.
Why statbel.catalog.list_views is rated Low
Tool queries and lists statistical metadata without modifying data or triggering external operations.
From the tool's definition Browse catalog, filterable by locale and name search, returns view metadata
Attacks that exploit this kind of access
The rule that runs statbel.catalog.list_views 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.list_views, this is the rule to start with:
statbel.catalog.list_views 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 statbel.catalog.list_views call is checked against it from then on.
Questions about statbel.catalog.list_views
Browse the Statbel beSTAT catalog of ~1300 curated, ready-to-query views (cross-tabs of Belgian official statistics), filterable by locale (fr/nl/de/en) and a case-insensitive name search. Each view exists as a separate record per language. Returns view_id, name, locale, and the backing data_source_id — use view_id with statbel.view_data to fetch the actual figures. Data: bestat.statbel.fgov.be, Belgian statistics office, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
statbel.catalog.list_views accepts 4 parameters: limit, locale, offset, search. 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.list_views: 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.list_views 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 statbel.catalog.list_views 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.list_views. 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.list_views 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