# compare_requirements

Compare how 2+ EU regulations treat the same compliance topic. Uses concept-synonym expansion (incident reporting → breach notification, ICT risk → risk management, etc.) and FTS5 search over chassis content. Returns a {results, meta} envelope: one cited row per matched provision (article number + snippet + per-article structured timelines + a source_url/publisher/license _citation), with meta.coverage and an explicit note for any regulation with no matches.

Agent View of the PolicyLayer registry record for `compare_requirements`. HTML page: https://policylayer.com/tools/eu-ansvar-eu-regulations-mcp/compare-requirements

## Facts

- Tool: `compare_requirements`
- Server: Eu Regulations (`https://gateway.ansvar.eu/mcp`) — https://policylayer.com/tools/eu-ansvar-eu-regulations-mcp.md
- Homepage: https://github.com/Ansvar-Systems/EU_compliance_MCP
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server auth posture: gated
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "compare_requirements",
    "arguments": {}
  }
}
```

## Why compare_requirements is rated Low

This tool retrieves and queries regulatory information to compare compliance requirements across EU regulations. It uses full-text search (FTS5) and concept expansion to find matching provisions, returning structured results with citations. All operations are read-only with no side effects—no data is created, modified, deleted, or executed.

From the tool's own definition: "Tool performs comparison and search operations: 'Compare how 2+ EU regulations treat the same compliance topic', 'FTS5 search over chassis content', 'Returns a {results, meta} envelope'. No modifications, deletions, or code execution. Pure data retrieval."

## Use case

AI agents call compare_requirements to retrieve information from Eu Regulations without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Eu Regulations:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "compare_requirements": {}
  }
}
```

## Other tools on Eu Regulations (4)

- `check_applicability` — Read — https://policylayer.com/tools/eu-ansvar-eu-regulations-mcp/check-applicability.md
- `get_evidence_requirements` — Read — https://policylayer.com/tools/eu-ansvar-eu-regulations-mcp/get-evidence-requirements.md
- `get_regulation_guide` — Read — https://policylayer.com/tools/eu-ansvar-eu-regulations-mcp/get-regulation-guide.md
- `map_controls` — Read — https://policylayer.com/tools/eu-ansvar-eu-regulations-mcp/map-controls.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=eu-ansvar-eu-regulations-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/eu-ansvar-eu-regulations-mcp