# 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}.

Agent View of the PolicyLayer registry record for `get_filing`. HTML page: https://policylayer.com/tools/com-filingfirehose-firehose/get-filing

## Facts

- Tool: `get_filing`
- Server: FilingFirehose (`https://filingfirehose.com/mcp`) — https://policylayer.com/tools/com-filingfirehose-firehose.md
- Homepage: https://github.com/jaablon/filingfirehose-python
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `accession_number` | string | yes |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_filing",
    "arguments": {
      "accession_number": "<accession_number>"
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches FilingFirehose:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_filing": {}
  }
}
```

## Other tools on FilingFirehose (3)

- `search_13d_filings` — Read — https://policylayer.com/tools/com-filingfirehose-firehose/search-13d-filings.md
- `search_8k_filings` — Read — https://policylayer.com/tools/com-filingfirehose-firehose/search-8k-filings.md
- `search_atm_offerings` — Read — https://policylayer.com/tools/com-filingfirehose-firehose/search-atm-offerings.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-filingfirehose-firehose · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-filingfirehose-firehose