get_source

get_source

Server Fred zachspar/fred-mcp
Category Read
Risk class Low
Parameters 00 required

What get_source does on Fred

AI agents call get_source 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.

Why get_source needs a policy

This tool retrieves source metadata from the FRED database—a public, read-only data source. There are no side effects, modifications, deletions, code execution, or financial transactions. The tool fits the 'Read' category as it queries and retrieves data without changing state.

From the tool's definition Tool name is 'get_source' and all sibling tools on the server (get_category, get_release, get_related_tags, etc.) follow a consistent pattern of retrieving FRED data.

Questions about get_source

What does the get_source tool do? +

get_source. It is categorised as a Read tool in the Fred MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_source? +

Register the Fred MCP server in PolicyLayer and add a rule for get_source: 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.

What risk level is get_source? +

get_source is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_source? +

Yes. Add a rate_limit block to the get_source 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.

How do I block get_source completely? +

Set action: deny in the PolicyLayer policy for get_source. 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.

What MCP server provides get_source? +

get_source 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.