MNPI Filter
The mnpi-filter policy blocks configured phrases during the output phase. It
uses detect_patterns or a small built-in list. A phrase match does not
determine that the information is material, non-public, or subject to
securities law.
Configuration
pack:
name: mnpi-filter
version: "1.0.0"
enabled: true
policies:
chain:
- mnpi-filter
policy:
mnpi-filter:
detect_patterns:
- "earnings before announcement"
- "merger not public"
- "insider information"
- "board decision"
Fields
| Field | Type | Description | Default |
|---|---|---|---|
detect_patterns | string[] | Phrases are not case-sensitive. An empty list uses the built-in list below. | built-in list |
action | block | This is the only accepted action. Each match causes a block. | block |
Built-in defaults
If you do not specify detect_patterns, the gateway uses this default list:
earnings before announcementmerger not publicinsider informationboard decisionnot public
How it works
- Output text: The gateway gets assistant text from the buffered response body.
- Pattern check: The gateway changes the text to lowercase and examines configured or built-in phrases.
- Context details: The policy records nearby terms such as
earnings,merger,ipo, oracquisition. - Verdict: A phrase match blocks the output with
reason_code = "mnpi.detected".
Important limitations
- This policy evaluates output text only.
- The policy does not support a configurable
warnorredactmode today. - The built-in list is small. Add phrases that apply to your organization.
- Use
stream: false. The active SSE path does not run this evaluator.
Correct examples
Default output block
pack:
name: mnpi-defaults
version: "1.0.0"
enabled: true
policies:
chain:
- mnpi-filter
policy:
mnpi-filter: {}
Add specified firm phrases
pack:
name: investment-banking-guardrail
version: "1.0.0"
enabled: true
policies:
chain:
- mnpi-filter
- financial-compliance
policy:
mnpi-filter:
detect_patterns:
- "earnings before announcement"
- "pending acquisition"
- "guidance revision not public"
- "board decision"
- "deal valuation confidential"
Best practices
- Replace or extend the defaults with phrases from your legal and compliance teams.
- Pair with
financial-compliancefor broader finance-output controls. - Review blocked events regularly. Change the phrase list after you find false results or missed phrases.
Next steps
- Financial Compliance — Finance-specific rewrite and block controls
- Audit Logger — Mark audit logging as active in the policy decision stream
- Trail and Audit Evidence — Examine and verify recorded decision evidence
- PII Detector — Sanitize sensitive identifiers in related workflows