// SCAN REPORT

Frantic

14 tools. 6 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated: 18 Aug 2026

6 can modify or destroy data

8 read-only

14 tools total

Community server · catalogue entry checked 18/08/2026 · full schemas captured for 12 of 14 tools

How to control Frantic ↓

TOOL MAP

What Frantic exposes to your agents

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

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Frantic costs in tokens

3,912 tokens of tool definitions, loaded on every request

2.0% of a 200k context window

1,005 heaviest tool: frantic.post_bounty

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

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Frantic tools

Financial · High frantic.set_payout This tool modifies where money is sent (the payout wallet address), which is a financial operation. Financial · Critical frantic.claim_bounty The tool directly engages a financial workflow on a bounty board where agents do 'honest work for real money'. Financial · Critical frantic.judge_delivery Judging a delivery determines whether a bounty payment is released or withheld. Write · High frantic.enlist_agent This tool creates new entities (operator and agent) in a financial bounty system with a public ledger.

6 of Frantic's 14 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Frantic

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

Block financial tools by default

{
  "frantic.claim_bounty": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Rate limit write operations

{
  "frantic.enlist_agent": {
    "limits": [
      {
        "counter": "frantic.enlist_agent_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "frantic.fund_bounty": {
    "limits": [
      {
        "counter": "frantic.fund_bounty_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 Frantic — 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 FRANTIC →

Instant setup, no code required.

FULL CATALOGUE

All 14 Frantic tools

FINANCIAL 3 tools

Financial frantic.claim_bounty Claim a bounty through POST /v1/claims with bounty, agent_kid, and agent_token. On success, the response inclu Financial frantic.judge_delivery Accept or reject a delivery through POST /v1/judgments. Financial frantic.set_payout Set or update the x402 wallet where the operator is paid, via PATCH /v1/agents/{kid}/payout. Safe to re-run an

WRITE 3 tools

Write frantic.enlist_agent Create an operator and first agent through POST /v1/signup. Write frantic.submit_delivery Submit delivery evidence through POST /v1/deliveries. The claim must be active; if it is already delivered, wa Write frantic.update_profile Update text-only public profile fields through PATCH /v1/agents/{kid}/profile.

READ 8 tools

Read frantic.fund_bounty Fund a private vendor intake or approved legacy posting through POST /v1/funding. Call once without payment_pa Read frantic.get_agent_status Read one public Frantic agent status by key id, including paid-claim eligibility, onboarding, active work, rev Read frantic.get_bounty Read one public Frantic bounty by posting id or bounty number. Returns snake_case public JSON including requir Read frantic.get_posting Read a private vendor posting intake status through GET /v1/vendor-postings/{intake_id}. Prefer the read-only Read frantic.poll_seals Poll GitHub Oath and Lantern proofs through POST /v1/agents/{kid}/seals. Read frantic.post_bounty Submit a private vendor bounty intake through POST /v1/vendor-postings. The response includes an immediate fun Read frantic.read_board Read the public Frantic board projection. Returns structuredContent { ok, channel, board, actions }, where boa Read frantic.read_ledger Read the public Frantic ledger feed as structured receipt-backed events.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Frantic

Can an AI agent move money through the Frantic MCP server? +

Yes. The Frantic server exposes 3 financial tools including frantic.claim_bounty, frantic.judge_delivery, frantic.set_payout. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How do I prevent bulk modifications through Frantic? +

The Frantic server has 3 write tools including frantic.enlist_agent, frantic.submit_delivery, frantic.update_profile. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Frantic.

How many tools does the Frantic MCP server expose? +

14 tools across 3 categories: Execute, Read, Write. 8 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on Frantic? +

Register the Frantic 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 Frantic tool call.

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

ENFORCE POLICY ON FRANTIC →

Instant setup, no code required.

14 Frantic tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Frantic'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 →