// SCAN REPORT

LebenslaufHeld

5 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 18 Aug 2026

1 can modify or destroy data

4 read-only

5 tools total

Community server · catalogue entry checked 18/08/2026 · full schemas captured for 4 of 5 tools

How to control LebenslaufHeld ↓

TOOL MAP

What LebenslaufHeld exposes to your agents

Read (4) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What LebenslaufHeld costs in tokens

3,083 tokens of tool definitions, loaded on every request

1.5% of a 200k context window

1,424 heaviest tool: lebenslauf_erstellen

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

High Risk

The most dangerous LebenslaufHeld tools

Write · Medium lebenslauf_erstellen This tool creates new CV documents (PDFs) from structured input data, which is a Write operation—it produces and stores new data artifacts reversibly.

1 of LebenslaufHeld's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control LebenslaufHeld

PolicyLayer is an MCP gateway — it sits between your AI agents and LebenslaufHeld, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "lebenslauf_erstellen": {
    "limits": [
      {
        "counter": "lebenslauf_erstellen_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "ats_check": {
    "limits": [
      {
        "counter": "ats_check_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register LebenslaufHeld — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON LEBENSLAUFHELD →

Instant setup, no code required.

FULL CATALOGUE

All 5 LebenslaufHeld tools

WRITE 1 tools

Write lebenslauf_erstellen Create a German CV as a real PDF in a professional design. Erstellt aus strukturierten Lebenslauf-Daten eine V

READ 4 tools

Read ats_check Deterministic ATS readability check for a resume PDF, no AI involved. Prueft ein Lebenslauf-PDF (Base64) rein Read beruf_beispiel Get a real example CV walkthrough for a specific profession. Liefert zu einem Berufsnamen das passende Beispie Read vollstaendigkeits_check Rule based completeness check for German CV data, no AI involved. Prueft Lebenslauf-Daten regelbasiert auf Pfl Read vorlagen_liste List all available CV template designs with preview image URLs. Listet alle LebenslaufHeld-Designvorlagen mit

FAQ

Questions about LebenslaufHeld

How do I prevent bulk modifications through LebenslaufHeld? +

The LebenslaufHeld server has 1 write tools including lebenslauf_erstellen. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach LebenslaufHeld.

How many tools does the LebenslaufHeld MCP server expose? +

5 tools across 2 categories: Read, Write. 4 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on LebenslaufHeld? +

Register the LebenslaufHeld MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every LebenslaufHeld tool call.

Deterministic rules across all 5 LebenslaufHeld tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON LEBENSLAUFHELD →

Instant setup, no code required.

5 LebenslaufHeld tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from LebenslaufHeld's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →