swissfso.table.query
Query data from any Swiss Federal Statistical Office (FSO/BFS) STAT-TAB dataset using dimension filters. Provide a database_id from catalog.list and optional filters (from table.metadata). Each filter specifies a dimension code and an array of value codes. Returns JSON-stat2 formatted data with d...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/swissfso.table.query.md
What swissfso.table.query does on Apibase
AI agents call swissfso.table.query 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 |
|---|---|---|---|
filters | array | — | Array of dimension filters. Unfiltered dimensions return all values. Tip: always filter time and region dimensions to keep response size manageable. |
database_id | string | Yes | BFS database identifier (e.g. "px-x-0304010000_201"). Use catalog.list to discover IDs; table.metadata to see variable codes and values. |
Parameters from the server's own tool schema.
Why swissfso.table.query is rated Low
Read-only query tool retrieving public statistical data with no side effects or modifications.
From the tool's definition Query data from Swiss Federal Statistical Office STAT-TAB dataset using dimension filters. Returns JSON-stat2 formatted data.
Risk signalsAccepts freeform code/query input (filters[].code)
Attacks that exploit this kind of access
The rule that runs swissfso.table.query 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 swissfso.table.query, this is the rule to start with:
swissfso.table.query 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 swissfso.table.query call is checked against it from then on.
Questions about swissfso.table.query
Query data from any Swiss Federal Statistical Office (FSO/BFS) STAT-TAB dataset using dimension filters. Provide a database_id from catalog.list and optional filters (from table.metadata). Each filter specifies a dimension code and an array of value codes. Returns JSON-stat2 formatted data with dimension labels and numeric values. Note: variable codes and labels are in German (official FSO data language). Unfiltered dimensions return all values, so always filter time and region to keep responses manageable. Swiss OGD, no auth. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
swissfso.table.query accepts 2 parameters: filters, database_id. Required: database_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 swissfso.table.query: 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.
swissfso.table.query 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 swissfso.table.query 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 swissfso.table.query. 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.
swissfso.table.query 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