Skip to main content

MCP: Enforcement Data

The Court Rules MCP server gives AI agents access to structured enforcement actions from the FTC, HHS, and 19 state attorneys general. Three tools let you search events, get full details, and aggregate statistics.

What you get

Three enforcement-focused tools: The same MCP server also provides six court rules tools for filing compliance. See MCP: Court Rules.

Quick start

Add the Court Rules MCP server to your client. Sample data works immediately, no API key needed.

Claude Code

Claude Desktop

Add to your Claude Desktop config:

Cursor

Add to ~/.cursor/mcp.json:

VS Code

Add to .vscode/mcp.json:

Codex CLI

Windsurf

Add to Windsurf MCP settings:
Once connected, try asking your agent: “What privacy enforcement actions happened in California this year?”

Sample vs Full access

The hosted MCP server has two access tiers: Sample data is available immediately, no sign-up needed. Try any tool to see real enforcement data before authenticating. To upgrade to full access, sign in at console.courtrules.app or contact api@courtrules.app. See Authentication for setup details.

Tool reference

search_enforcement_actions

Search privacy and regulatory enforcement events. Filters combine with AND logic. Parameters: Example response:

get_enforcement_details

Get full details for a specific enforcement event, including laws cited, remedies, and verbatim source quotes. Parameters: Example response:

get_enforcement_stats

Aggregate enforcement data by dimension. Parameters: Example response (group_by: “jurisdiction”):

Integration patterns

Regulatory feed widget

Use search_enforcement_actions with jurisdiction and industry filters to surface relevant enforcement events in your legal workspace. Poll periodically for new events.

Auto-matter creation

When a relevant enforcement event appears, automatically create a matter in your legal workspace:

Agent-powered research

Combine tools for research queries:

Polling for new events

The MCP server does not push notifications when new enforcement events are added. To check for new events, poll search_enforcement_actions with a date_from filter set to your last check time:
For platform integrations that auto-create matters, run this on a schedule (e.g., every 6 hours) and process any new events.

Response field reference

Key fields in enforcement event responses, with types and null semantics:

Error handling

MCP tool calls return errors as text content, not HTTP error codes. If a tool encounters an error (invalid parameters, database unavailable), the response will contain a descriptive error message in the content array:
Common error patterns:
  • Invalid event_id: "No enforcement event found with ID \"...\"."
  • Invalid group_by: "Invalid group_by value \"...\". Must be one of: jurisdiction, violation_type, risk_level, month"
  • Database error: "Error querying enforcement data: ..."
The hosted server at mcp.courtrules.app does not currently enforce rate limits on MCP tool calls.

Current limitations

  • No webhooks yet: Poll for new events using date_from filters
  • No real-time streaming: Events appear within 24-48 hours of government announcement
  • Read-only: The MCP server provides data access only, no write operations
  • Auth optional: Sample data works without authentication. OAuth unlocks the full dataset.
For higher throughput or custom filtering, use the REST API directly.

Next steps