Read a specific section from an SEC Source (10-K, 10-Q, 8-K earnings, 8-K events, or DEF 14A proxy). Two modes: 1. Section mode (default) — pass section_id for full paginated text (up to 10 chunks per page). 2. Outline mode — OMIT section_id and pass accession_number to receive the filing's secti...
Risk signalsAccepts freeform code/query input (query) · High parameter count (17 properties)
Part of the MetricDuck — Financial Analysis server.
Free to start. No card required.
AI agents call get_filing_section 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 get_filing_section 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.
{
"version": "1",
"default": "deny",
"tools": {
"get_filing_section": {}
}
}See the full MetricDuck — Financial Analysis policy for all 22 tools.
These attack patterns abuse exactly the kind of access get_filing_section gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Read a specific section from an SEC Source (10-K, 10-Q, 8-K earnings, 8-K events, or DEF 14A proxy). Two modes: 1. Section mode (default) — pass section_id for full paginated text (up to 10 chunks per page). 2. Outline mode — OMIT section_id and pass accession_number to receive the filing's section TOC with ~120-char content previews per section. Use this when drilling into an unfamiliar Source (multi-exhibit 8-K, DEF 14A, FPI 6-K) to pick the right section by content rather than guessing from section_id. Use list_filings first to discover accession numbers. In section mode, omitting accession_number returns the latest filing's section. The section_id field description (below) enumerates valid IDs by category. Use Cases: - "Apple risk factors" -> get_filing_section("AAPL", "risk_factors") - "Customer concentration in NVDA" -> get_filing_section("NVDA", "risk_factors", query="customer concentration") - "Workforce / headcount / employees by geography" -> get_filing_section("MSFT", "business_description", query="human capital") (Human Capital Resources lives in Item 1, not a separate section) - "M&A terms" -> get_filing_section("CVX", "item_1_01_material_agreement", form_type="8-K") - "As of a past date / point-in-time" -> get_filing_section("MSFT", "business_description", vantage_date="2025-04-07") (serves the latest 10-K filed on/before that date — use this for time-anchored questions instead of assuming the newest filing; or pin an exact report via accession_number from list_filings) - "Multi-exhibit 8-K" -> get_filing_section(ticker, accession_number="...") (outline mode) → pick exhibit → get_filing_section(ticker, section_id="item_7_01_exhibit_99_02") Sister Sources (non-SEC): - Earnings call transcripts → compare_earnings_calls (cross-quarter view) or list_filings + section_id="transcript_prepared_remarks" - IR press releases / events → screen_filing_signals with signal_type="ir_press_release" - Raw XBRL dimensional facts → get_xbrl_facts Delisted / acquired issuers: pass cik (10-digit, zero-padded) instead of ticker and set include_delisted=true. Examples: SAVE Spirit Airlines (cik="0001498710"), RDFN Redfin (cik="0001382821"). Responses capped at ~20K chars. Use offset for pagination or query to narrow results.. It is categorised as a Read tool in the MetricDuck — Financial Analysis MCP Server, which means it retrieves data without modifying state.
Register the MetricDuck — Financial Analysis MCP server in PolicyLayer and add a rule for get_filing_section: 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.
get_filing_section is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_filing_section 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.
Set action: deny in the PolicyLayer policy for get_filing_section. 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.
get_filing_section 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.
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.