// SCAN REPORT

Fred

31 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 30 Jun 2026

0 can modify or destroy data

31 read-only

31 tools total

Community server · catalogue entry verified 30/06/2026

How to control Fred ↓

TOOL MAP

What Fred exposes to your agents

Read (31) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Fred

PolicyLayer is an MCP gateway — it sits between your AI agents and Fred, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "get_category": {
    "limits": [
      {
        "counter": "get_category_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Fred — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FRED →

Instant setup, no code required.

FULL CATALOGUE

All 31 Fred tools

READ 31 tools

Read get_category get_category Read get_category_children get_category_children Read get_category_related get_category_related Read get_category_related_tags get_category_related_tags Read get_category_series get_category_series Read get_category_tags get_category_tags Read get_related_tags get_related_tags Read get_release get_release Read get_release_dates get_release_dates Read get_release_related_tags get_release_related_tags Read get_release_series get_release_series Read get_release_sources get_release_sources Read get_release_tables get_release_tables Read get_release_tags get_release_tags Read get_series get_series Read get_series_categories get_series_categories Read get_series_observations get_series_observations Read get_series_release get_series_release Read get_series_tags get_series_tags Read get_series_updates get_series_updates Read get_series_vintage_dates get_series_vintage_dates Read get_source get_source Read get_source_releases get_source_releases Read get_tags_series get_tags_series Read list_release_dates list_release_dates Read list_releases list_releases Read list_sources list_sources Read search_series search_series Read search_series_related_tags search_series_related_tags Read search_series_tags search_series_tags

FAQ

Questions about Fred

Is the Fred MCP server safe to use without restrictions? +

The Fred server is primarily read-only with 31 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Fred MCP server expose? +

31 tools across 1 categories: Read. 31 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Fred? +

Register the Fred MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Fred tool call.

Deterministic rules across all 31 Fred tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FRED →

Instant setup, no code required.

31 Fred tools catalogued and risk-classified — across an index of 43,000+ MCP servers.