bea_state_economic_history

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Medium RISK CLASS

Category Write

Parameters 72 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/bea-state-economic-history.md

WHAT IT DOES

What bea_state_economic_history does on Livedatalink

AI agents use bea_state_economic_history to create or update resources in Livedatalink, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livedatalink environment.

Parameter	Type	Required	Description
`limit`	integer	—	Maximum years. Default 20.
`offset`	integer	—	Years to skip. Default 0.
`end_year`	integer	—	Four-digit calendar year. Hosted source coverage is reported in every response.
`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
`start_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.

RISK

Why bea_state_economic_history is rated Medium

An AI agent can call bea_state_economic_history faster than any human can review: one bad instruction and it creates or modifies resources in Livedatalink by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bea_state_economic_history 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_history, this is the rule to start with:

bea_state_economic_history Rate-limited

bea_state_economic_history stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bea_state_economic_history": {
      "limits": [
        {
          "counter": "bea_state_economic_history_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every bea_state_economic_history call is checked against it from then on.

FAQ

Questions about bea_state_economic_history

What does the bea_state_economic_history tool do? +

Return bounded annual history for one official BEA SASUMMARY state or U.S. indicator. Includes exact value, unit, state GeoFIPS, pagination, source update date, evidence hash, and attribution. Use this for 'Texas real GDP since 2018', 'California per-capita income history', or 'US employment by year'. Published aggregate annual estimates only; BEA can revise prior vintages. It is categorised as a Write tool in the Livedatalink MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does bea_state_economic_history accept? +

bea_state_economic_history accepts 7 parameters: limit, offset, end_year, geography, indicator, start_year, response_format. Required: geography, indicator. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on bea_state_economic_history? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for bea_state_economic_history: 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.

What risk level is bea_state_economic_history? +

bea_state_economic_history is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bea_state_economic_history? +

Yes. Add a rate_limit block to the bea_state_economic_history 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.

How do I block bea_state_economic_history completely? +

Set action: deny in the PolicyLayer policy for bea_state_economic_history. 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.

What MCP server provides bea_state_economic_history? +

bea_state_economic_history 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.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 381 Livedatalink tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →