swissfso.table.metadata
Get the variable dimensions and available filter values for any Swiss Federal Statistical Office (FSO/BFS) STAT-TAB dataset. Provide a database_id from catalog.list. Returns the table title, dimension codes, and all available value codes with German labels — needed to construct filters for table....
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/swissfso.table.metadata.md
What swissfso.table.metadata does on Apibase
AI agents call swissfso.table.metadata 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 |
|---|---|---|---|
database_id | string | Yes | BFS database identifier (e.g. "px-x-0304010000_201" for monthly wages, "px-x-0103010000_123" for 2023 population by canton). Obtain from catalog.list. |
Parameters from the server's own tool schema.
Why swissfso.table.metadata is rated Low
Retrieves metadata about dataset structure without modifying data or executing operations with side effects.
From the tool's definition Get the variable dimensions and available filter values for any dataset. Returns table title, dimension codes, and available value codes.
Attacks that exploit this kind of access
The rule that runs swissfso.table.metadata 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.metadata, this is the rule to start with:
swissfso.table.metadata 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.metadata call is checked against it from then on.
Questions about swissfso.table.metadata
Get the variable dimensions and available filter values for any Swiss Federal Statistical Office (FSO/BFS) STAT-TAB dataset. Provide a database_id from catalog.list. Returns the table title, dimension codes, and all available value codes with German labels — needed to construct filters for table.query. Example: database_id "px-x-0304010000_201" returns year, region, industry, professional status, gender, and percentile dimensions for monthly gross wages. Data: Swiss OGD, no auth, commercial use permitted. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
swissfso.table.metadata accepts 1 parameter: 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.metadata: 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.metadata 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.metadata 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.metadata. 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.metadata 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