AI agents call get_source_releases 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.
The tool appears to retrieve/query releases linked to a specific source within the FRED database. This is a passive read operation with no side effects, consistent with the server's purpose of enabling data queries. The absence of modification, deletion, or execution keywords, combined with the pattern of sibling 'get_*' tools, confirms this is Read category.
From the tool's definition Tool name 'get_source_releases' indicates retrieval of releases associated with a source. Server description emphasizes 'querying and retrieving Federal Reserve Economic Data' with operations like 'get_release', 'get_category', and other sibling tools that…
Attacks that exploit this kind of access
get_source_releases. 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_source_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 Fred. Nothing to install.
get_source_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 get_source_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 get_source_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.
get_source_releases 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 →