Low Risk

bls_get_series

Fetch historical time series data for employment, inflation, wages, productivity, or housing. Returns dated data points with values. Provide series ID (e.g., "PAYEMS" for total nonfarm employment).

Part of the Bls server.

bls_get_series is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE BLS →

Free to start. No card required.

AI agents call bls_get_series to retrieve information from Bls without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though bls_get_series only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "bls_get_series": {}
  }
}

See the full Bls policy for all 24 tools.

Get this rule live on your own Bls server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY BLS →

View all 24 tools →

These attack patterns abuse exactly the kind of access bls_get_series gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so bls_get_series only ever does what you allow.

SECURE BLS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the bls_get_series tool do? +

Fetch historical time series data for employment, inflation, wages, productivity, or housing. Returns dated data points with values. Provide series ID (e.g., "PAYEMS" for total nonfarm employment).. It is categorised as a Read tool in the Bls MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bls_get_series? +

Register the Bls MCP server in PolicyLayer and add a rule for bls_get_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 Bls. Nothing to install.

What risk level is bls_get_series? +

bls_get_series is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bls_get_series? +

Yes. Add a rate_limit block to the bls_get_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.

How do I block bls_get_series completely? +

Set action: deny in the PolicyLayer policy for bls_get_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.

What MCP server provides bls_get_series? +

bls_get_series is provided by the Bls MCP server (https://gateway.pipeworx.io/bls/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Bls tool call.

Deterministic rules across all 24 Bls tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.