bls.macro.cpi
Get U.S. Consumer Price Index (CPI-U) data by item category and year range. Returns monthly values, year-over-year percentage change, and a full data series. Categories: "all" = All Items (headline inflation), "food", "energy", "shelter", "core" = All Items Less Food and Energy. Covers data from ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/bls.macro.cpi.md
What bls.macro.cpi does on Apibase
AI agents call bls.macro.cpi 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 |
|---|---|---|---|
item | string | — | CPI category: "all" = All Items CPI-U (default), "food" = Food, "energy" = Energy, "shelter" = Shelter, "core" = All Items Less Food and Energy. |
end_year | integer | — | Last year of CPI data (default: current year). |
start_year | integer | — | First year of CPI data (default: current year - 4). |
Parameters from the server's own tool schema.
Why bls.macro.cpi is rated Low
Queries historical U.S. inflation data without modifying, deleting, or executing operations.
From the tool's definition retrieves CPI data by category and year range; returns monthly values and data series
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bls.macro.cpi 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 bls.macro.cpi, this is the rule to start with:
bls.macro.cpi 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 bls.macro.cpi call is checked against it from then on.
Questions about bls.macro.cpi
Get U.S. Consumer Price Index (CPI-U) data by item category and year range. Returns monthly values, year-over-year percentage change, and a full data series. Categories: "all" = All Items (headline inflation), "food", "energy", "shelter", "core" = All Items Less Food and Energy. Covers data from 1913 (All Items) through the most recently released month. Ideal for inflation analysis, cost-of-living calculations, real-return adjustments, and economic research. Data source: BLS Consumer Expenditure Survey, CPI-U series (urban consumers). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
bls.macro.cpi accepts 3 parameters: item, end_year, 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 bls.macro.cpi: 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.
bls.macro.cpi 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 bls.macro.cpi 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 bls.macro.cpi. 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.
bls.macro.cpi 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