sec_filing_decoder
Décodeur de filing SEC — Gapup agent-payable C-suite expertise (CFO). Returns a structured, audited deliverable. Answers: Read the 10-K of <ticker> and give me the material red flags, KPI movements, and a board-ready executive summary. · What has materially changed in <ticker>'s risk profile in i...
This record as markdown: /tools/io-github-getgapup-gapup-mcp/sec-filing-decoder.md
What sec_filing_decoder does on Gapup Mcp
AI agents use sec_filing_decoder to commit financial operations through Gapup Mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
cik | string | — | |
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
focus | string | Yes | |
ticker | string | — | |
filing_types | array | Yes | |
lookback_months | integer | Yes |
Parameters from the server's own tool schema.
Why sec_filing_decoder is rated Critical
The tool is described as 'agent-payable' with 'x402 per-call' billing, meaning each invocation commits a financial transaction. The underlying data operation is Read (retrieving and analyzing SEC filings), but the payment-per-call model places it in the Financial category per the severity hierarchy. An AI agent autonomously invoking this tool repeatedly could accumulate significant charges.
From the tool's definition Gapup agent-payable ... x402 per-call; CFO-level deliverable covering KPI movements, M&A signals, due-diligence briefs, going-concern flags
Attacks that exploit this kind of access
The rule that runs sec_filing_decoder safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sec_filing_decoder, this is the rule to start with:
Any call to sec_filing_decoder is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gapup Mcp, apply this rule, and every sec_filing_decoder call is checked against it from then on.
Questions about sec_filing_decoder
Décodeur de filing SEC — Gapup agent-payable C-suite expertise (CFO). Returns a structured, audited deliverable. Answers: Read the 10-K of <ticker> and give me the material red flags, KPI movements, and a board-ready executive summary. · What has materially changed in <ticker>'s risk profile in its latest annual filing? Flag any going-concern or auditor-change signals. · Is there any M&A signal or strategic review hint in <ticker>'s most recent SEC filings? What's the evidence? · Prepare a due-diligence SEC filing brief for <ticker>: financial snapshot, red flags, governance changes, and recommended next actions. · What is the sentiment of <ticker>'s latest 10-K compared to its most recent 10-Q — bullish, neutral, or bearish? Reference case: SHOP · 10-K FY2024 · 4 red flags (1 critical: merchant concentration) · Revenue +24.7% YoY · . Inputs are validated server-side — send the documented case fields. It is categorised as a Financial tool in the Gapup Mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
sec_filing_decoder accepts 6 parameters: cik, async, focus, ticker, filing_types, lookback_months. Required: focus, filing_types, lookback_months. The full parameter table on this page comes from the server's own tool schema.
Register the Gapup MCP server in PolicyLayer and add a rule for sec_filing_decoder: 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 Gapup Mcp. Nothing to install.
sec_filing_decoder is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sec_filing_decoder 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 sec_filing_decoder. 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.
sec_filing_decoder is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
Across the catalogue