# get_evidence_requirements

Get audit-evidence requirements for an EU regulation. Returns a {results, meta} envelope: one cited row per requirement with artifact name, example, retention period, auditor questions, maturity-level expectations, and a source_url/publisher/license _citation to the requirement\

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

## Facts

- Tool: `get_evidence_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": "get_evidence_requirements",
    "arguments": {}
  }
}
```

## Why get_evidence_requirements is rated Low

This tool retrieves audit-evidence requirements from EU regulations (GDPR, NIS2, DORA, AI Act). It queries existing regulatory data and returns structured information about requirements, examples, and audit questions. There are no side effects, no data modification, no execution of external operations, and no destructive actions.

From the tool's own definition: "Tool description states it 'Returns a {results, meta} envelope: one cited row per requirement with artifact name, example, retention period, auditor questions, maturity-level expectations, and a source_url/publisher/license _citation' - purely retrieves and…"

## Use case

AI agents call get_evidence_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": {
    "get_evidence_requirements": {}
  }
}
```

## Other tools on Eu Regulations (4)

- `check_applicability` — Read — https://policylayer.com/tools/eu-ansvar-eu-regulations-mcp/check-applicability.md
- `compare_requirements` — Read — https://policylayer.com/tools/eu-ansvar-eu-regulations-mcp/compare-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