statbel.catalog.view_data
Fetch the full set of fact rows (flat cross-tab, columns vary per view) for one Statbel beSTAT view, identified by the view_id from statbel.list_views. Data: bestat.statbel.fgov.be, Belgian statistics office, no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/statbel.catalog.view-data.md
What statbel.catalog.view_data does on Apibase
AI agents call statbel.catalog.view_data 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 |
|---|---|---|---|
view_id | string | Yes | View UUID from statbel.list_views (e.g. "1be9b77f-4005-4d58-a885-8281b5bbe617"). Already encodes the language — no separate locale param needed. |
Parameters from the server's own tool schema.
Why statbel.catalog.view_data is rated Low
Retrieves statistical data from public Belgian statistics database with no side effects.
From the tool's definition Fetch the full set of fact rows for one Statbel beSTAT view
Attacks that exploit this kind of access
The rule that runs statbel.catalog.view_data 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.view_data, this is the rule to start with:
statbel.catalog.view_data 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.view_data call is checked against it from then on.
Questions about statbel.catalog.view_data
Fetch the full set of fact rows (flat cross-tab, columns vary per view) for one Statbel beSTAT view, identified by the view_id from statbel.list_views. 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.view_data accepts 1 parameter: view_id. Required: view_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.view_data: 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.view_data 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.view_data 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.view_data. 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.view_data 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