Get personal income by county from the BEA Regional accounts (CAINC1 table). Returns total personal income for a county or state total. When year is omitted, returns the last 5 available years. GeoFips format: 5-digit county FIPS (e.g. '53067') or state total (e.g. '53000'). Args: county_fips: 5-...
Part of the BEA Economic Accounts server.
Free to start. No card required.
AI agents call get_county_personal_income to retrieve information from BEA Economic Accounts without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_county_personal_income only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_county_personal_income": {}
}
}See the full BEA Economic Accounts policy for all 5 tools.
These attack patterns abuse exactly the kind of access get_county_personal_income gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get personal income by county from the BEA Regional accounts (CAINC1 table). Returns total personal income for a county or state total. When year is omitted, returns the last 5 available years. GeoFips format: 5-digit county FIPS (e.g. '53067') or state total (e.g. '53000'). Args: county_fips: 5-digit county FIPS code (e.g. '53067') or state total (e.g. '53000'). year: Specific year to retrieve. Omit for last 5 years.. It is categorised as a Read tool in the BEA Economic Accounts MCP Server, which means it retrieves data without modifying state.
Register the BEA Economic Accounts MCP server in PolicyLayer and add a rule for get_county_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 BEA Economic Accounts. Nothing to install.
get_county_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 get_county_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 get_county_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.
get_county_personal_income is provided by the BEA Economic Accounts MCP server (https://mcp.olyport.com/bea/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 BEA Economic Accounts tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.