// SCAN REPORT

Framekeep Public Discovery

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

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

Last updated: 18 Aug 2026

0 can modify or destroy data

3 read-only

3 tools total

Community server · catalogue entry checked 18/08/2026

How to control Framekeep Public Discovery ↓

TOOL MAP

What Framekeep Public Discovery exposes to your agents

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

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Framekeep Public Discovery costs in tokens

121 tokens of tool definitions, loaded on every request

0.1% of a 200k context window

43 heaviest tool: get_framekeep_start_options

Full per-tool breakdown → Model it in the token calculator →

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 Framekeep Public Discovery

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

Cap read operations

{
  "get_framekeep_overview": {
    "limits": [
      {
        "counter": "get_framekeep_overview_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 Framekeep Public Discovery — 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 FRAMEKEEP PUBLIC DISCOVERY →

Instant setup, no code required.

FULL CATALOGUE

All 3 Framekeep Public Discovery tools

READ 3 tools

Read get_framekeep_overview Return a concise public overview of Framekeep and its privacy boundaries. Read get_framekeep_start_options Return privacy-safe links for creating a free no-account gallery or a reusable studio. Read list_framekeep_public_resources List Framekeep's preferred public documentation and discovery URLs.

FAQ

Questions about Framekeep Public Discovery

Is the Framekeep Public Discovery MCP server safe to use without restrictions? +

The Framekeep Public Discovery server is primarily read-only with 3 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 Framekeep Public Discovery MCP server expose? +

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

How do I enforce a policy on Framekeep Public Discovery? +

Register the Framekeep Public Discovery 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 Framekeep Public Discovery tool call.

Deterministic rules across all 3 Framekeep Public Discovery tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FRAMEKEEP PUBLIC DISCOVERY →

Instant setup, no code required.

3 Framekeep Public Discovery tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Framekeep Public Discovery's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →