Low Risk

sec_report_search

Use when you need narrative content from SEC filings — risk factors, MD&A, guidance language, deal terms, accounting policies, share structure. For consolidated financial numbers use run_sql on financial_statements instead. Semantic search over the full text of company-filed SEC filings; returns ...

Risk signalsAccepts freeform code/query input (query)

Part of the Drillr — The financial MCP for AI agents server.

sec_report_search 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 DRILLR — THE FINANCIAL MCP FOR AI AGENTS →

Free to start. No card required.

AI agents call sec_report_search to retrieve information from Drillr — The financial MCP for AI agents 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 sec_report_search 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": {
    "sec_report_search": {}
  }
}

See the full Drillr — The financial MCP for AI agents policy for all 9 tools.

Get this rule live on your own Drillr — The financial MCP for AI agents server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DRILLR — THE FINANCIAL MCP FOR AI AGENTS →

View all 9 tools →

These attack patterns abuse exactly the kind of access sec_report_search 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 sec_report_search only ever does what you allow.

SECURE DRILLR — THE FINANCIAL MCP FOR AI AGENTS →

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

What does the sec_report_search tool do? +

Use when you need narrative content from SEC filings — risk factors, MD&A, guidance language, deal terms, accounting policies, share structure. For consolidated financial numbers use run_sql on financial_statements instead. Semantic search over the full text of company-filed SEC filings; returns matching passages. Parameters: - query (required): natural-language search; phrase it as the concept or section name you want, e.g. "share repurchase authorization", "Risk Factors", "segment revenue". Run a few phrasings rather than one broad query. - ticker (required): the company whose filings to search. - filing_types (optional): array to restrict to specific types — 10-K (US annual), 10-Q (US quarterly), 8-K (US current/material events), 20-F (foreign annual), 6-K (foreign current), DEF 14A (proxy), S-1/F-1 (IPO), + amendments. OMIT to search all types — foreign issuers (e.g. BABA, TSM) file 20-F/6-K, so omitting avoids zero results. - period_start / period_end (optional): yyyy-mm window; set both to narrow to a date range, omit to search all history. - top_k (optional): max passages to return (default 5). Scope: indexes ONLY company-filed reports — NOT institutional filings (13F-HR/13D/13G; for those use insider_and_institution_activities with source='institution'). Filings carry narrative, not structured numbers — for revenue/margins/EPS use financial_statements first. Section targets (search the named section for the intent): non-GAAP / adjusted figures + reconciliations → earnings 8-K (Exhibit 99.1); dilution / SBC / buyback → "Shareholders' Equity" or "Capital Stock"; risk factors → "Risk Factors"; segment breakdown → "Segment Information"; management guidance → "Outlook" / "Guidance" in MD&A; exec comp / board → DEF 14A; accounting policies → "Critical Accounting Policies"; properties → "Properties".. It is categorised as a Read tool in the Drillr — The financial MCP for AI agents MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sec_report_search? +

Register the Drillr — The financial MCP for AI agents MCP server in PolicyLayer and add a rule for sec_report_search: 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 Drillr — The financial MCP for AI agents. Nothing to install.

What risk level is sec_report_search? +

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

Can I rate-limit sec_report_search? +

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

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

sec_report_search is provided by the Drillr — The financial MCP for AI agents MCP server (https://gateway.drillr.ai/mcp/data). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Drillr — The financial MCP for AI agents tool call.

Deterministic rules across all 9 Drillr — The financial MCP for AI agents 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.