Low Risk

edgar_company_filings

AUTHORITATIVE list of recent SEC filings for a specific US public company. Pass a ticker ("AAPL") or CIK ("320193"). Filter by form type — "10-K" (annual report), "10-Q" (quarterly), "8-K" (material event — but for severity-classified 8-Ks specifically, prefer sec_8k_recent), "DEF 14A" (proxy), "...

Part of the Edgar server.

edgar_company_filings 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 EDGAR →

Free to start. No card required.

AI agents call edgar_company_filings to retrieve information from Edgar 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 edgar_company_filings 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": {
    "edgar_company_filings": {}
  }
}

See the full Edgar policy for all 25 tools.

Get this rule live on your own Edgar server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY EDGAR →

View all 25 tools →

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

SECURE EDGAR →

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

What does the edgar_company_filings tool do? +

AUTHORITATIVE list of recent SEC filings for a specific US public company. Pass a ticker ("AAPL") or CIK ("320193"). Filter by form type — "10-K" (annual report), "10-Q" (quarterly), "8-K" (material event — but for severity-classified 8-Ks specifically, prefer sec_8k_recent), "DEF 14A" (proxy), "S-1" (IPO registration), etc. Returns filing dates, form types, accession numbers, document links. Use for "what did $TICKER recently file" or "show me the last N proxy statements for $TICKER". For specific financial metrics over time use edgar_company_concept; for the full XBRL dump use edgar_company_facts.. It is categorised as a Read tool in the Edgar MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on edgar_company_filings? +

Register the Edgar MCP server in PolicyLayer and add a rule for edgar_company_filings: 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 Edgar. Nothing to install.

What risk level is edgar_company_filings? +

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

Can I rate-limit edgar_company_filings? +

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

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

edgar_company_filings is provided by the Edgar MCP server (https://gateway.pipeworx.io/edgar/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Edgar tool call.

Deterministic rules across all 25 Edgar 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.