AI agents call list_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 or lists release dates from FRED—a query operation with no side effects. It fits the Read category. Severity is low because even if misused, querying public economic data poses minimal risk. Confidence is 0.85 rather than higher only because the tool description is empty, but the naming convention and server context make the classification clear.
From the tool's definition Tool name 'list_release_dates' indicates data retrieval. Server description states it 'retrieves Federal Reserve Economic Data' with operations like 'get_release_dates' and other sibling tools are all read operations (get_*, list_*).
Attacks that exploit this kind of access
list_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 list_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.
list_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 list_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 list_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.
list_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 →