Critical Risk →

dilution_filings

S-3 shelf registrations and 424B5 takedowns for a ticker — both signal share issuance. S-3 = the shelf authorization itself (lower immediate impact); 424B5 = actual sale off the shelf (higher impact, often -3% announcement reaction per Loughran-Ritter). Returns parsed shelf amount and use-of-proc...

Part of the Openinsider MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

openinsider-mcp Destructive

AI agents may call dilution_filings to permanently remove or destroy resources in Openinsider. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call dilution_filings in a loop, permanently destroying resources in Openinsider. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

openinsider.yaml
tools:
  dilution_filings:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Openinsider policy for all 16 tools.

Tool Name dilution_filings
Category Destructive
Risk Level Critical

View all 16 tools →

Agents calling destructive-class tools like dilution_filings have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

dilution_filings is one of the critical-risk operations in Openinsider. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the dilution_filings tool do? +

S-3 shelf registrations and 424B5 takedowns for a ticker — both signal share issuance. S-3 = the shelf authorization itself (lower immediate impact); 424B5 = actual sale off the shelf (higher impact, often -3% announcement reaction per Loughran-Ritter). Returns parsed shelf amount and use-of-proceeds excerpt when extractable. Use when: - User asks 'is TICKER raising money' or 'why is TICKER weak today' - Pre-earnings or pre-catalyst dilution-risk check - Following up on a sudden price drop on heavy volume Important context: small-cap biotech S-3 takedowns are frequently pre-PDUFA capital raises (interpret in biotech context); non-biotech 424B5s are more directly bearish.. It is categorised as a Destructive tool in the Openinsider MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on dilution_filings? +

Add a rule in your Intercept YAML policy under the tools section for dilution_filings. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Openinsider MCP server.

What risk level is dilution_filings? +

dilution_filings is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit dilution_filings? +

Yes. Add a rate_limit block to the dilution_filings rule in your Intercept 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 dilution_filings completely? +

Set action: deny in the Intercept policy for dilution_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 dilution_filings? +

dilution_filings is provided by the Openinsider MCP server (openinsider-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.