bea_state_economic_trend
Calculate prior-observation and exact five-year changes for one official BEA SASUMMARY state indicator. Returns component observations, absolute and percent changes, five-year CAGR when meaningful, units, vintage evidence, and caveats. Use this for 'five-year Florida GDP trend', 'how has Ohio emp...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/bea-state-economic-trend.md
What bea_state_economic_trend does on Livedatalink
AI agents call bea_state_economic_trend to retrieve information from Livedatalink 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 |
|---|---|---|---|
geography | string | Yes | State name, USPS abbreviation, 5-digit state-summary GeoFIPS, or United States/US. |
indicator | string | Yes | Supported indicator slug/name or BEA SASUMMARY line code; examples: gdp, real_gdp, personal_income, per_capita_personal_income, regional_price_parities, total_e |
as_of_year | integer | — | Four-digit calendar year. Hosted source coverage is reported in every response. |
response_format | string | — | Human-readable markdown or machine-readable JSON. Default markdown. |
Parameters from the server's own tool schema.
Why bea_state_economic_trend is rated Low
Even though bea_state_economic_trend only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs bea_state_economic_trend safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bea_state_economic_trend, this is the rule to start with:
bea_state_economic_trend 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 Livedatalink, apply this rule, and every bea_state_economic_trend call is checked against it from then on.
Questions about bea_state_economic_trend
Calculate prior-observation and exact five-year changes for one official BEA SASUMMARY state indicator. Returns component observations, absolute and percent changes, five-year CAGR when meaningful, units, vintage evidence, and caveats. Use this for 'five-year Florida GDP trend', 'how has Ohio employment changed?', or 'California real per-capita income growth'. The optional as-of year prevents future observations from entering a historical calculation. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
bea_state_economic_trend accepts 4 parameters: geography, indicator, as_of_year, response_format. Required: geography, indicator. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for bea_state_economic_trend: 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 Livedatalink. Nothing to install.
bea_state_economic_trend 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_state_economic_trend 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_state_economic_trend. 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_state_economic_trend is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue