AI agents call get_release_dates 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 economic data release dates from FRED—a public economic database. It has no side effects, creates no data modifications, executes no code, and poses minimal risk. The get_* naming convention and context of sibling retrieval tools confirm it is a simple query operation. Severity is low because the worst outcome would be information disclosure of already-public Federal Reserve data.
From the tool's definition Tool name 'get_release_dates' indicates a read operation. Server description states it 'Enables querying and retrieving Federal Reserve Economic Data' with operations like 'get_release', 'get_release_series', and other get-prefixed methods, all of which are…
Attacks that exploit this kind of access
get_release_dates. 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_dates: 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_dates 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_dates 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_dates. 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_dates 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 →