ecb-rates.macro.money_supply
Get the euro area M3 monetary aggregate — outstanding amount at end of period, working-day and seasonally adjusted, in EUR. M3 is the broad money supply measure the ECB monitors as a reference value for monetary policy. Monthly series. Filter by last_n_observations or start_period/end_period. Dat...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ecb-rates.macro.money-supply.md
What ecb-rates.macro.money_supply does on Apibase
AI agents call ecb-rates.macro.money_supply 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 |
|---|---|---|---|
end_period | string | — | End of date range: YYYY, YYYY-MM, or YYYY-MM-DD depending on series frequency. Ignored if last_n_observations is set. |
start_period | string | — | Start of date range: YYYY, YYYY-MM, or YYYY-MM-DD depending on series frequency. Ignored if last_n_observations is set. |
last_n_observations | integer | — | Return only the most recent N observations (max 100). Takes precedence over start_period/end_period. Default 10 if no range given. |
Parameters from the server's own tool schema.
Why ecb-rates.macro.money_supply is rated Low
Retrieves historical monetary supply data with no side effects or modifications possible.
From the tool's definition Get the euro area M3 monetary aggregate, monthly series, filter observations, data warehouse query.
Attacks that exploit this kind of access
The rule that runs ecb-rates.macro.money_supply 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 ecb-rates.macro.money_supply, this is the rule to start with:
ecb-rates.macro.money_supply 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 ecb-rates.macro.money_supply call is checked against it from then on.
Questions about ecb-rates.macro.money_supply
Get the euro area M3 monetary aggregate — outstanding amount at end of period, working-day and seasonally adjusted, in EUR. M3 is the broad money supply measure the ECB monitors as a reference value for monetary policy. Monthly series. Filter by last_n_observations or start_period/end_period. Data: ECB Statistical Data Warehouse (data-api.ecb.europa.eu), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ecb-rates.macro.money_supply accepts 3 parameters: end_period, start_period, last_n_observations. 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 ecb-rates.macro.money_supply: 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.
ecb-rates.macro.money_supply 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 ecb-rates.macro.money_supply 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 ecb-rates.macro.money_supply. 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.
ecb-rates.macro.money_supply 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