imf.macro.inflation
Get inflation rate (average consumer prices, annual percent change) from the IMF World Economic Outlook (WEO) for one or more countries, including IMF forward projections. Filter by ISO 3166-1 alpha-3 country code(s) and/or a year range; omit filters to get all 190+ countries plus regional/income...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/imf.macro.inflation.md
What imf.macro.inflation does on Apibase
AI agents call imf.macro.inflation 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 |
|---|---|---|---|
country | string | — | ISO 3166-1 alpha-3 country code to filter (e.g. "USA", "DEU", "JPN", "CHN"). Omit to return all 190+ countries plus IMF regional/income-group aggregates. |
end_year | integer | — | Latest year to include, including IMF WEO forward projections (e.g. 2029). Omit for full history. |
countries | array | — | List of ISO 3166-1 alpha-3 country codes to filter (e.g. ["USA","DEU","JPN"]), max 20. Use instead of "country" to fetch multiple countries in one call. |
start_year | integer | — | Earliest year to include in the returned time series (e.g. 2015). Omit for full history. |
Parameters from the server's own tool schema.
Why imf.macro.inflation is rated Low
Retrieves historical and projected inflation data from public IMF sources without side effects.
From the tool's definition Get inflation rate, query, no auth required, read-only economic data
Attacks that exploit this kind of access
The rule that runs imf.macro.inflation 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 imf.macro.inflation, this is the rule to start with:
imf.macro.inflation 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 imf.macro.inflation call is checked against it from then on.
Questions about imf.macro.inflation
Get inflation rate (average consumer prices, annual percent change) from the IMF World Economic Outlook (WEO) for one or more countries, including IMF forward projections. Filter by ISO 3166-1 alpha-3 country code(s) and/or a year range; omit filters to get all 190+ countries plus regional/income-group aggregates. Data: IMF DataMapper (www.imf.org), CC BY 4.0, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
imf.macro.inflation accepts 4 parameters: country, end_year, countries, start_year. 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 imf.macro.inflation: 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.
imf.macro.inflation 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 imf.macro.inflation 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 imf.macro.inflation. 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.
imf.macro.inflation 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