swissnbm.money.aggregates
Retrieve Swiss monetary aggregate statistics published by the Swiss National Bank: currency in circulation, sight deposits, M1 (narrowest money), savings deposits, M2, time deposits, and M3 (broadest money supply). Values in CHF millions (level) or percent period-over-period change. Data updated ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/swissnbm.money.aggregates.md
What swissnbm.money.aggregates does on Apibase
AI agents call swissnbm.money.aggregates 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 | — | Number of most recent monthly observations to return per aggregate (1–120, default 24). |
level_type | string | — | Data type: "level" for absolute CHF million values (default) or "change" for period-over-period percent change. |
Parameters from the server's own tool schema.
Why swissnbm.money.aggregates is rated Low
Tool retrieves published macroeconomic data without modification, deletion, or financial transaction capability.
From the tool's definition Retrieve Swiss monetary aggregate statistics, currency in circulation, sight deposits, M1, M2, M3.
Attacks that exploit this kind of access
The rule that runs swissnbm.money.aggregates 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 swissnbm.money.aggregates, this is the rule to start with:
swissnbm.money.aggregates 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 swissnbm.money.aggregates call is checked against it from then on.
Questions about swissnbm.money.aggregates
Retrieve Swiss monetary aggregate statistics published by the Swiss National Bank: currency in circulation, sight deposits, M1 (narrowest money), savings deposits, M2, time deposits, and M3 (broadest money supply). Values in CHF millions (level) or percent period-over-period change. Data updated monthly; most recent observations typically available with a 4–6 week lag. Ideal for Swiss monetary conditions analysis, inflation research, and macroeconomic studies. Source: Swiss National Bank data.snb.ch (cube: snbmonagg), Swiss OGD open license, no auth. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
swissnbm.money.aggregates accepts 2 parameters: limit, level_type. 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 swissnbm.money.aggregates: 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.
swissnbm.money.aggregates 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 swissnbm.money.aggregates 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 swissnbm.money.aggregates. 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.
swissnbm.money.aggregates 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