fred_releases
Browse FRED economic releases (e.g. Employment Situation, CPI, GDP). With upcoming_dates=true, returns the upcoming release calendar instead. Useful for knowing when fresh data is expected.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fred-releases.md
What fred_releases does on Livedatalink
AI agents call fred_releases 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 | number | — | Maximum rows to return (default 50 for observations, 25 for catalog queries). |
release_id | number | — | Optional. If provided, return only that release's metadata. |
upcoming_dates | boolean | — | If true, return upcoming release date schedule instead of release metadata. Default false. |
Parameters from the server's own tool schema.
Why fred_releases is rated Low
This tool retrieves publicly available economic data from the Federal Reserve Economic Data (FRED) system. It performs passive lookups of release schedules and historical releases without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—at worst, an agent retrieves irrelevant economic calendars, which causes no harm.
From the tool's definition Tool description states 'Browse FRED economic releases' and 'returns the upcoming release calendar' — both read-only retrieval operations with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
The rule that runs fred_releases 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 fred_releases, this is the rule to start with:
fred_releases 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 fred_releases call is checked against it from then on.
Questions about fred_releases
Browse FRED economic releases (e.g. Employment Situation, CPI, GDP). With upcoming_dates=true, returns the upcoming release calendar instead. Useful for knowing when fresh data is expected. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fred_releases accepts 3 parameters: limit, release_id, upcoming_dates. 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 fred_releases: 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.
fred_releases 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 fred_releases 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 fred_releases. 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.
fred_releases 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