bls_indicator
US labor & price statistics from the Bureau of Labor Statistics by friendly name. Available: unemployment_rate, labor_force_participation, employment_population_ratio, cpi, cpi_less_food_energy, nonfarm_payrolls, avg_hourly_earnings, avg_weekly_hours, ppi_final_demand. Returns a monthly time seri...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/bls-indicator.md
What bls_indicator does on Livedatalink
AI agents call bls_indicator 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 |
|---|---|---|---|
end_year | number | — | End year (optional; defaults to current year). |
indicator | string | — | Indicator name, one of: unemployment_rate, labor_force_participation, employment_population_ratio, cpi, cpi_less_food_energy, nonfarm_payrolls, avg_hourly_earni |
start_year | number | — | Start year (optional; defaults to ~3 years back). |
Parameters from the server's own tool schema.
Why bls_indicator is rated Low
This tool performs a simple data retrieval operation querying public economic statistics. There are no side effects, no data modification, no code execution, and no destructive operations. Even if misused by an AI agent, the worst outcome would be retrieving publicly available information. The severity is low because the data is official, public, and unauthenticated.
From the tool's definition Tool description explicitly states it 'Returns a monthly time series' of public Bureau of Labor Statistics data. No modification, deletion, or execution capabilities are mentioned.
Attacks that exploit this kind of access
The rule that runs bls_indicator 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 bls_indicator, this is the rule to start with:
bls_indicator 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 bls_indicator call is checked against it from then on.
Questions about bls_indicator
US labor & price statistics from the Bureau of Labor Statistics by friendly name. Available: unemployment_rate, labor_force_participation, employment_population_ratio, cpi, cpi_less_food_energy, nonfarm_payrolls, avg_hourly_earnings, avg_weekly_hours, ppi_final_demand. Returns a monthly time series. Keyless official BLS data. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
bls_indicator accepts 3 parameters: end_year, indicator, start_year. 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 bls_indicator: 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.
bls_indicator 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 bls_indicator 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 bls_indicator. 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.
bls_indicator 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