bea.regional.state_gdp
Retrieve real GDP by US state from the BEA Regional Economic Accounts (CAGDP2 table). Returns GDP in thousands of dollars for all 50 states + DC + US total by year and industry component (agriculture, mining, manufacturing, finance, real estate, government, etc.). Use for state-level economic ana...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/bea.regional.state-gdp.md
What bea.regional.state_gdp does on Apibase
AI agents call bea.regional.state_gdp 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 |
geo_fips | string | — | Geographic FIPS code(s) to retrieve. "STATE" (default) returns all 50 US states + DC, "COUNTY" for all counties, "MSA" for metro areas, or a specific 5-digit FI |
line_code | integer | — | CAGDP2 line code for the GDP component. 1=All industry total (default), 2=Private industries, 3=Agriculture/forestry/fishing, 6=Mining, 10=Utilities, 11=Constru |
Parameters from the server's own tool schema.
Why bea.regional.state_gdp is rated Low
Retrieves historical economic data with no side effects or modifications to systems.
From the tool's definition Retrieve real GDP by US state from the BEA Regional Economic Accounts
Attacks that exploit this kind of access
The rule that runs bea.regional.state_gdp 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.regional.state_gdp, this is the rule to start with:
bea.regional.state_gdp 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.regional.state_gdp call is checked against it from then on.
Questions about bea.regional.state_gdp
Retrieve real GDP by US state from the BEA Regional Economic Accounts (CAGDP2 table). Returns GDP in thousands of dollars for all 50 states + DC + US total by year and industry component (agriculture, mining, manufacturing, finance, real estate, government, etc.). Use for state-level economic analysis, regional comparisons, and industry cluster research. GeoFips parameter supports individual state FIPS codes, all states, MSAs, or counties. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
bea.regional.state_gdp accepts 3 parameters: year, geo_fips, line_code. 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.regional.state_gdp: 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.regional.state_gdp 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.regional.state_gdp 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.regional.state_gdp. 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.regional.state_gdp 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