Why teams use enforcement data
In-house legal teams need to know when regulators take action in their industry. An event against a competitor or a vendor can lead to a contract review, a policy update or a report to the board. Each event is a structured, searchable record with a link to its press release, so it can feed your legal workflows directly. Common uses:- Watch the enforcement events that affect your industry.
- Scan vendor contracts when a new type of violation appears, using the
search_termsof an event. - Create a matter in your legal workspace when a high-risk event appears.
- Track enforcement by jurisdiction or violation type for compliance reports.
What an event contains
Example search
Callsearch_privacy_enforcement_actions with filters to find the events you need:
search_privacy_enforcement_actions reference.
Jurisdictions
The data covers the FTC and state regulators. To list the jurisdictions available today, callget_privacy_enforcement_stats with group_by set to jurisdiction. Use the codes it returns in the jurisdiction filter.
Violation types
Each event carries one or more violation types, in four groups:Risk levels
Each event has a risk level, which depends on the fine and the remedies:Access methods
You can reach the enforcement data in two ways.- The MCP server has three tools,
search_privacy_enforcement_actions,get_privacy_enforcement_actionandget_privacy_enforcement_stats. See MCP: enforcement data. - The web console lets you browse and filter events at courtrules.app/enforcement.
Data freshness
The enforcement data is updated daily, and a new event appears after the next daily check. To get only the events since your last check, callsearch_privacy_enforcement_actions with date_from. One call a day is enough:
date_from to find new events.