AI agents call get_category_related 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 designed to retrieve relationships between FRED categories, which is a read-only query operation with no side effects. The empty description reduces confidence slightly, but the naming convention and server's stated purpose as a data retrieval service for public economic data strongly indicate this is a safe read operation with minimal blast radius if misused.
From the tool's definition Tool name 'get_category_related' follows the get_* pattern consistent with sibling read-only tools (get_category, get_release, get_related_tags, etc.).
Attacks that exploit this kind of access
get_category_related. 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_category_related: 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_category_related 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_category_related 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_category_related. 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_category_related 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 →