AI agents call get_release to retrieve information from Fred without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves release information from the Federal Reserve Economic Data (FRED) system. It has no side effects—it only queries and returns data. The tool name 'get_release' combined with the server's stated purpose of 'querying and retrieving' and the consistent read-only pattern of all sibling tools confirms this is a safe data retrieval operation with minimal risk.
From the tool's definition Tool name 'get_release' and server context showing FRED data retrieval; sibling tools all follow read-only pattern (get_category, get_release_dates, get_release_related_tags, get_release_series).
Attacks that exploit this kind of access
get_release. It is categorised as a Read tool in the Fred MCP Server, which means it retrieves data without modifying state.
Register the Fred MCP server in PolicyLayer and add a rule for get_release: 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 Fred. Nothing to install.
get_release 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 get_release 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 get_release. 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.
get_release is provided by the Fred MCP server (zachspar/fred-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →