// SCAN REPORT

FilingFirehose

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

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

Last updated: 3 Aug 2026

0 can modify or destroy data

4 read-only

4 tools total

Community server · catalogue entry checked 03/08/2026 · full schemas captured for 4 of 4 tools

How to control FilingFirehose ↓

TOOL MAP

What FilingFirehose exposes to your agents

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

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What FilingFirehose costs in tokens

1,077 tokens of tool definitions, loaded on every request

0.5% of a 200k context window

337 heaviest tool: search_8k_filings

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 FilingFirehose

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

Cap read operations

{
  "get_filing": {
    "limits": [
      {
        "counter": "get_filing_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 FilingFirehose — 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 FILINGFIREHOSE →

Instant setup, no code required.

FULL CATALOGUE

All 4 FilingFirehose tools

READ 4 tools

Read get_filing Fetch one filing by SEC accession number, regardless of recency. Useful when an agent has an accession nu Read search_13d_filings Search recent SEC Schedule 13D / 13G filings from the past 72 hours. Args: activist: Filter to fi Read search_8k_filings Search recent SEC 8-K filings (current report) from the past 72 hours. Args: items: Comma-separat Read search_atm_offerings Search recent SEC at-the-market (ATM) equity offerings from the past 72 hours. Pulls from S-3 / 424B5 fam

FAQ

Questions about FilingFirehose

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

The FilingFirehose server is primarily read-only with 4 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 FilingFirehose MCP server expose? +

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

How do I enforce a policy on FilingFirehose? +

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

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

ENFORCE POLICY ON FILINGFIREHOSE →

Instant setup, no code required.

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

// WHERE THIS COMES FROM

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