bea_search_state_indicators
Search the 15 indicators in LiveDataLink's self-hosted official BEA SASUMMARY annual state snapshot. Returns canonical indicator names, definitions, units, exact coverage, pagination, evidence hash, and attribution. Use this for 'what BEA state measures are hosted?', 'find regional price parity',...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/bea-search-state-indicators.md
What bea_search_state_indicators does on Livedatalink
AI agents call bea_search_state_indicators 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 |
|---|---|---|---|
limit | integer | — | Maximum results. Default 20. |
query | string | — | Optional words matched against indicator name, definition, and unit. |
offset | integer | — | Results to skip. Default 0. |
response_format | string | — | Human-readable markdown or machine-readable JSON. Default markdown. |
Parameters from the server's own tool schema.
Why bea_search_state_indicators is rated Low
Even though bea_search_state_indicators 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_search_state_indicators 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_search_state_indicators, this is the rule to start with:
bea_search_state_indicators 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_search_state_indicators call is checked against it from then on.
Questions about bea_search_state_indicators
Search the 15 indicators in LiveDataLink's self-hosted official BEA SASUMMARY annual state snapshot. Returns canonical indicator names, definitions, units, exact coverage, pagination, evidence hash, and attribution. Use this for 'what BEA state measures are hosted?', 'find regional price parity', or to resolve an indicator before a history call. Scope is the compact annual state summary, not the full BEA API or industry detail. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
bea_search_state_indicators accepts 4 parameters: limit, query, offset, response_format. 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_search_state_indicators: 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_search_state_indicators 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_search_state_indicators 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_search_state_indicators. 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_search_state_indicators 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