bls_series
Fetch any BLS time series by its raw series ID (e.g. 'LNS14000000' for the unemployment rate, or a state/industry series). For when you know the exact BLS series ID.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/bls-series.md
What bls_series does on Livedatalink
AI agents call bls_series 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). |
series_id | string | Yes | BLS series ID, e.g. 'LNS14000000'. |
start_year | number | — | Start year (optional). |
Parameters from the server's own tool schema.
Why bls_series is rated Low
This tool retrieves public time series data from the Bureau of Labor Statistics based on a series ID parameter. It performs a straightforward query operation with no side effects, data modification, code execution, or financial impact. The data returned is historical economic statistics that are publicly available. This is a classic Read operation.
From the tool's definition Tool description explicitly states 'Fetch any BLS time series' and provides examples of retrieving unemployment data by series ID. The verb 'fetch' indicates data retrieval with no modification or execution.
Attacks that exploit this kind of access
The rule that runs bls_series 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_series, this is the rule to start with:
bls_series 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_series call is checked against it from then on.
Questions about bls_series
Fetch any BLS time series by its raw series ID (e.g. 'LNS14000000' for the unemployment rate, or a state/industry series). For when you know the exact BLS series ID. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
bls_series accepts 3 parameters: end_year, series_id, start_year. Required: series_id. 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_series: 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_series 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_series 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_series. 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_series 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