Enroll customers into your AML screening vendor's ongoing monitoring profile using their name, date of birth, and any existing matched entity references
Configure the monitoring profile with the list categories to watch (SDN, PEP, adverse media) and the alert sensitivity threshold
Subscribe to the vendor's monitoring alert webhook or polling endpoint for new match notifications
On receipt of a new alert, retrieve the full match detail and route it to the appropriate compliance queue based on list type and match confidence
Define and document your periodic re-screening frequency (monthly, quarterly, or annually) based on customer risk tier and regulatory requirements
Implement a scheduled job that triggers full re-screening for all monitored customers at the required interval and logs the re-screening event for audit
Known gotchas
Ongoing monitoring detects new matches as lists are updated, but it does not retroactively re-score historical matches; run periodic full re-screens separately
Alert fatigue is a real risk; tune alert thresholds carefully and track the false positive rate to ensure compliance staff can process genuine alerts in a timely manner
Customer data used in monitoring profiles must be kept current; stale name or DOB data will cause missed matches if a customer's information changes
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp