# vollstaendigkeits_check

Rule based completeness check for German CV data, no AI involved. Prueft Lebenslauf-Daten regelbasiert auf Pflichtangaben, empfohlene Angaben und optionale Angaben nach deutschen Bewerbungsstandards.

Agent View of the PolicyLayer registry record for `vollstaendigkeits_check`. HTML page: https://policylayer.com/tools/de-lebenslaufheld-mcp/vollstaendigkeits-check

## Facts

- Tool: `vollstaendigkeits_check`
- Server: LebenslaufHeld (`https://lebenslaufheld.de/mcp`) — https://policylayer.com/tools/de-lebenslaufheld-mcp.md
- Homepage: https://github.com/https://lebenslaufheld.de/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `daten` | object | yes |  |

Parameters from the server's own tool schema.

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

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

## Why vollstaendigkeits_check is rated Low

This is a data validation and analysis tool with no side effects. It reads CV data, applies predefined rules, and reports findings. The lack of auth and anonymous design confirms this is a read-only inspection utility. Severity is low because misuse would at worst generate false validation feedback, which has minimal business or security impact.

From the tool's own definition: "Tool performs a rule-based completeness check that examines CV data against German application standards for mandatory, recommended, and optional fields."

## Use case

AI agents call vollstaendigkeits_check to retrieve information from LebenslaufHeld 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 LebenslaufHeld:

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

## Other tools on LebenslaufHeld (4)

- `ats_check` — Read — https://policylayer.com/tools/de-lebenslaufheld-mcp/ats-check.md
- `beruf_beispiel` — Read — https://policylayer.com/tools/de-lebenslaufheld-mcp/beruf-beispiel.md
- `vorlagen_liste` — Read — https://policylayer.com/tools/de-lebenslaufheld-mcp/vorlagen-liste.md
- `lebenslauf_erstellen` — Write — https://policylayer.com/tools/de-lebenslaufheld-mcp/lebenslauf-erstellen.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=de-lebenslaufheld-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/de-lebenslaufheld-mcp