fred_compare
Compare 2 to 5 FRED series side-by-side over the same date range. Returns observations for each series. Useful for ratio analysis (e.g. compare 10Y vs 2Y yield) or cross-series correlation.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fred-compare.md
What fred_compare does on Livedatalink
AI agents call fred_compare 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 | string | — | Inclusive upper-bound ISO date (YYYY-MM-DD). |
limit | number | — | Maximum rows to return (default 50 for observations, 25 for catalog queries). |
start | string | — | Inclusive lower-bound ISO date (YYYY-MM-DD). |
series_ids | array | Yes | 2 to 5 FRED series IDs. |
Parameters from the server's own tool schema.
Why fred_compare is rated Low
This tool retrieves and returns economic data observations from FRED (Federal Reserve Economic Data) for comparison purposes. It is purely a read/query operation with no side effects, data modification, or financial transactions involved.
From the tool's definition Compare 2 to 5 FRED series side-by-side over the same date range. Returns observations for each series.
Attacks that exploit this kind of access
The rule that runs fred_compare 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_compare, this is the rule to start with:
fred_compare 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_compare call is checked against it from then on.
Questions about fred_compare
Compare 2 to 5 FRED series side-by-side over the same date range. Returns observations for each series. Useful for ratio analysis (e.g. compare 10Y vs 2Y yield) or cross-series correlation. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fred_compare accepts 4 parameters: end, limit, start, series_ids. Required: series_ids. 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_compare: 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_compare 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_compare 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_compare. 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_compare 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