bea.national.personal_income
Retrieve US Personal Income and Outlays from BEA NIPA Table T20100 (millions of dollars). Covers total personal income, compensation of employees, proprietors income, rental income, personal interest income, dividends, personal taxes, disposable personal income, and personal savings. Annual or qu...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/bea.national.personal-income.md
What bea.national.personal_income does on Apibase
AI agents call bea.national.personal_income 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 |
|---|---|---|---|
year | string | — | Year(s) to retrieve. Single year (e.g. "2023"), comma-separated list ("2021,2022,2023"), "LAST5" for latest 5 years, "LAST10" for latest 10, or "X"/"ALL" for al |
frequency | string | — | Data frequency: A=Annual, Q=Quarterly, M=Monthly. Multiple values comma-separated (e.g. "A,Q"). Defaults to A. |
Parameters from the server's own tool schema.
Why bea.national.personal_income is rated Low
Tool queries historical economic data without modifying systems or committing financial transactions.
From the tool's definition Retrieve US Personal Income and Outlays from BEA NIPA Table
Attacks that exploit this kind of access
The rule that runs bea.national.personal_income 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 bea.national.personal_income, this is the rule to start with:
bea.national.personal_income 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 bea.national.personal_income call is checked against it from then on.
Questions about bea.national.personal_income
Retrieve US Personal Income and Outlays from BEA NIPA Table T20100 (millions of dollars). Covers total personal income, compensation of employees, proprietors income, rental income, personal interest income, dividends, personal taxes, disposable personal income, and personal savings. Annual or quarterly frequency, covering all years since 1929. Essential for consumer spending analysis and household financial health tracking. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
bea.national.personal_income accepts 2 parameters: year, frequency. 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 bea.national.personal_income: 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.
bea.national.personal_income 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 bea.national.personal_income 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 bea.national.personal_income. 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.
bea.national.personal_income 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