Low Risk

search_sec_filings

Search the full text of every SEC filing since 2001 to find companies related to any concept — a product, technology, regulation, event, or company. Returns filing-level results with aggregated statistics (company count, form type breakdown, industry distribution). For 10-K/10-Q filings processed...

Risk signalsAccepts freeform code/query input (query) · Bulk/mass operation — affects multiple targets

Part of the MetricDuck — Financial Analysis server.

search_sec_filings is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE METRICDUCK — FINANCIAL ANALYSIS →

Free to start. No card required.

AI agents call search_sec_filings to retrieve information from MetricDuck — Financial Analysis without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though search_sec_filings only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_sec_filings": {}
  }
}

See the full MetricDuck — Financial Analysis policy for all 22 tools.

Get this rule live on your own MetricDuck — Financial Analysis server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY METRICDUCK — FINANCIAL ANALYSIS →

View all 22 tools →

These attack patterns abuse exactly the kind of access search_sec_filings gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so search_sec_filings only ever does what you allow.

SECURE METRICDUCK — FINANCIAL ANALYSIS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the search_sec_filings tool do? +

Search the full text of every SEC filing since 2001 to find companies related to any concept — a product, technology, regulation, event, or company. Returns filing-level results with aggregated statistics (company count, form type breakdown, industry distribution). For 10-K/10-Q filings processed by MetricDuck, also shows WHICH SECTIONS contain the term with drill-in pointers. Searchable form types (all SEC forms since 2001): - 10-K, 10-Q — Annual/quarterly reports (section-level drill-down available) - 8-K — Material events, earnings announcements, leadership changes - DEF 14A, DEFM14A, PRE 14A — Proxy statements: executive compensation, board proposals, merger votes - S-1, F-1 — IPO registration statements (new market entrants, competitive landscape) - S-3, S-4 — Shelf registrations, M&A registration statements - 424B series — Prospectus supplements (debt/equity offerings) - N-CSR, N-CSRS — Fund annual/semi-annual reports (institutional positioning) - SD — Conflict minerals disclosure (physical supply chain mapping) - SC 13D, SC 13G — Beneficial ownership (activist investors, large holders) - 20-F, 40-F, 6-K — Foreign private issuer reports - Any other SEC form type — omit form_type to search all The FORM TYPE reveals the context: - 10-K risk factors → dependency, competition, or regulatory exposure - 10-K revenue footnote / business description → customer/supplier/partner - 8-K → material event reaction or announcement - S-1 → new market entrant (IPO in your space) - DEF 14A → executive compensation tied to a metric or initiative - SD → physical supply chain (minerals, manufacturing) - SC 13D → activist investor targeting a company Section-level enrichment (10-K/10-Q only): For MetricDuck-processed filings, results include which sections contain the term (risk factors, MD&A, revenue footnote, etc.) with chunk pointers for immediate drill-in via get_filing_section. Non-standard forms (S-1, DEF 14A, etc.) return filing metadata and accession numbers but no section-level detail. Use cases: - "Who supplies Apple?" → ticker_lookup="AAPL" → companies listing Apple in revenue footnotes - "Recent data breaches?" → query="cybersecurity incident", form_type="8-K" - "Tariff-exposed companies?" → query="tariff", form_type="10-K" → risk factor disclosures - "Activist campaigns?" → query="board representation", form_type="DEF 14A,SC 13D" When to use other tools instead: - You already know the company → get_filing_index (signal triage) or list_filings (filing inventory) - You want financial metrics → screen_companies (numeric filters) - You want earnings call cross-quarter view → compare_earnings_calls Key limitation: keyword matching only, not semantic. "No material weakness" matches "material weakness found." Verify hits with get_filing_section for context. Search tips: quoted exact phrases ("material weakness"); proximity NEAR(5); OR / NOT; trailing wildcards (restructur*). Historical event queries (M&A announcements, lawsuits, restructurings, leadership changes): the default 1-year date_from and rank_by="date" ordering bury historical anchors under mutual-fund NPORT-P holdings. For specific events, prefer form_type="8-K" + widen date_from to before the event + rank_by="relevance" — this surfaces the anchor 8-K in the top results instead of fund noise.. It is categorised as a Read tool in the MetricDuck — Financial Analysis MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_sec_filings? +

Register the MetricDuck — Financial Analysis MCP server in PolicyLayer and add a rule for search_sec_filings: 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 MetricDuck — Financial Analysis. Nothing to install.

What risk level is search_sec_filings? +

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

Can I rate-limit search_sec_filings? +

Yes. Add a rate_limit block to the search_sec_filings 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 search_sec_filings completely? +

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

search_sec_filings is provided by the MetricDuck — Financial Analysis MCP server (https://mcp.metricduck.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MetricDuck — Financial Analysis tool call.

Deterministic rules across all 22 MetricDuck — Financial Analysis tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.