bea_state_economic_profile

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

High RISK CLASS

Category Execute

Parameters 31 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-profile.md

WHAT IT DOES

What bea_state_economic_profile does on Livedatalink

AI agents invoke bea_state_economic_profile to trigger actions in Livedatalink. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`geography`	string	Yes	State name, USPS abbreviation, 5-digit state-summary GeoFIPS, or United States/US.
`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.

RISK

Why bea_state_economic_profile is rated High

bea_state_economic_profile triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

bea_state_economic_profile Rate-limited

bea_state_economic_profile stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_profile": {
      "limits": [
        {
          "counter": "bea_state_economic_profile_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_profile call is checked against it from then on.

FAQ

Questions about bea_state_economic_profile

What does the bea_state_economic_profile tool do? +

Build a compact official BEA annual economic profile for one state or the United States across all 15 hosted SASUMMARY indicators: GDP, income, consumer spending, per-capita measures, regional price levels, and jobs. Each value carries its own year and unit because source update calendars differ. Use this for 'BEA profile for North Carolina', 'state GDP income jobs packet', or as the BEA leg of a regional market brief combined with Census, BLS, SBA, FDIC, or housing data. Aggregate estimates only; not a forecast or investment recommendation. It is categorised as a Execute tool in the Livedatalink MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does bea_state_economic_profile accept? +

bea_state_economic_profile accepts 3 parameters: geography, as_of_year, response_format. Required: geography. 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_profile? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for bea_state_economic_profile: 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_profile? +

bea_state_economic_profile is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit bea_state_economic_profile? +

Yes. Add a rate_limit block to the bea_state_economic_profile 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_profile completely? +

Set action: deny in the PolicyLayer policy for bea_state_economic_profile. 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_profile? +

bea_state_economic_profile 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →