Low Risk

list_recent_filings

Discover recent SEC filings landed since a watermark — single call, universe-wide, optional portfolio filter. Use this when: building event-driven agent workflows (Routines, alerts, daily portfolio checks). The right primitive when the question is "what new filings have landed?" rather than "what...

Part of the MetricDuck — Financial Analysis server.

list_recent_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 METRICDUCK — FINANCIAL ANALYSIS →

Free to start. No card required.

AI agents call list_recent_filings 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 list_recent_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": {
    "list_recent_filings": {}
  }
}

See the full MetricDuck — Financial Analysis policy for all 22 tools.

Get this rule live on your own MetricDuck — Financial Analysis server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY METRICDUCK — FINANCIAL ANALYSIS →

View all 22 tools →

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

SECURE METRICDUCK — FINANCIAL ANALYSIS →

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

What does the list_recent_filings tool do? +

Discover recent SEC filings landed since a watermark — single call, universe-wide, optional portfolio filter. Use this when: building event-driven agent workflows (Routines, alerts, daily portfolio checks). The right primitive when the question is "what new filings have landed?" rather than "what filings does this one company have?". Returns: flat list of {ticker, accession, filed_at, form_type, form_subtype}, newest first. form_subtype is computed from the filing's section inventory: '8-K-earnings' (has any earnings_* section), '8-K-transcript' (has any transcript_* section), '8-K-event' (has any item_* section), '8-K-other' (8-K with none of the above), or null for non-8-K forms. Cost: ~one call regardless of portfolio size — vs O(N) calls if you fan out per-ticker via list_filings. Composition: for each row in the result, drill in via get_filing_index(ticker, accession_number=...) to get the signal map of that specific filing, then get_filing_section for narrative content. Use list_filings instead when: you need ALL filings for ONE company (paginate by year). list_recent_filings is the cross-company / event-discovery primitive; list_filings is the per-company catalog.. It is categorised as a Read tool in the MetricDuck — Financial Analysis MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_recent_filings? +

Register the MetricDuck — Financial Analysis MCP server in PolicyLayer and add a rule for list_recent_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 MetricDuck — Financial Analysis. Nothing to install.

What risk level is list_recent_filings? +

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

Can I rate-limit list_recent_filings? +

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

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

list_recent_filings 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.

Enforce policy on every MetricDuck — Financial Analysis tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.