get_filing
Fetch one filing by SEC accession number, regardless of recency. Useful when an agent has an accession number from a citation or earlier tool call and needs the parsed details. Args: accession_number: SEC accession in 'XXXXXXXXXX-YY-NNNNNN' format. Returns: JSON for the filing if found in our arc...
This record as markdown: /tools/com-filingfirehose-firehose/get-filing.md
What get_filing does on FilingFirehose
AI agents call get_filing to retrieve information from FilingFirehose without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
accession_number | string | Yes |
Parameters from the server's own tool schema.
Why get_filing is rated Low
This tool purely retrieves and queries existing SEC EDGAR filing data from an archive. It accepts a filing identifier and returns structured data without any write, destructive, execute, or financial operations. The low severity reflects that fetching public SEC filings poses minimal risk of misuse—the data is already public and read-only access cannot harm systems or data integrity.
From the tool's definition Tool description states 'Fetch one filing' and 'Returns: JSON for the filing if found in our archive'. The function retrieves parsed SEC filing data by accession number with no modification, deletion, or execution capability. No side effects are performed.
Attacks that exploit this kind of access
The rule that runs get_filing safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FilingFirehose, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_filing, this is the rule to start with:
get_filing is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FilingFirehose, apply this rule, and every get_filing call is checked against it from then on.
Questions about get_filing
Fetch one filing by SEC accession number, regardless of recency. Useful when an agent has an accession number from a citation or earlier tool call and needs the parsed details. Args: accession_number: SEC accession in 'XXXXXXXXXX-YY-NNNNNN' format. Returns: JSON for the filing if found in our archive, or {"found": false}. It is categorised as a Read tool in the FilingFirehose MCP Server, which means it retrieves data without modifying state.
get_filing accepts 1 parameter: accession_number. Required: accession_number. The full parameter table on this page comes from the server's own tool schema.
Register the FilingFirehose MCP server in PolicyLayer and add a rule for get_filing: 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 FilingFirehose. Nothing to install.
get_filing 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 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. 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 is provided by the FilingFirehose MCP server (https://filingfirehose.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FilingFirehose, and thousands of servers like it.
This server
Across the catalogue