ats_check
Deterministic ATS readability check for a resume PDF, no AI involved. Prueft ein Lebenslauf-PDF (Base64) rein technisch auf Maschinenlesbarkeit fuer Bewerbungssysteme: Text-Layer, Schriften, Datumsformate, Standard-Ueberschriften.
This record as markdown: /tools/de-lebenslaufheld-mcp/ats-check.md
What ats_check does on LebenslaufHeld
AI agents call ats_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
pdf_base64 | string | Yes |
Parameters from the server's own tool schema.
Why ats_check is rated Low
This tool analyzes and reports on properties of an uploaded PDF document without modifying it, deleting it, or triggering external operations. It is purely a read/query operation that returns ATS compatibility metrics. The analysis is deterministic and technical, with no side effects beyond generating a compliance report.
From the tool's definition Tool performs a 'Deterministic ATS readability check' that 'Prueft ein Lebenslauf-PDF...rein technisch auf Maschinenlesbarkeit' (checks a resume PDF purely technically for machine readability).
Attacks that exploit this kind of access
The rule that runs ats_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and LebenslaufHeld, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ats_check, this is the rule to start with:
ats_check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect LebenslaufHeld, apply this rule, and every ats_check call is checked against it from then on.
Questions about ats_check
Deterministic ATS readability check for a resume PDF, no AI involved. Prueft ein Lebenslauf-PDF (Base64) rein technisch auf Maschinenlesbarkeit fuer Bewerbungssysteme: Text-Layer, Schriften, Datumsformate, Standard-Ueberschriften. It is categorised as a Read tool in the LebenslaufHeld MCP Server, which means it retrieves data without modifying state.
ats_check accepts 1 parameter: pdf_base64. Required: pdf_base64. The full parameter table on this page comes from the server's own tool schema.
Register the LebenslaufHeld MCP server in PolicyLayer and add a rule for ats_check: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches LebenslaufHeld. Nothing to install.
ats_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ats_check rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for ats_check. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
ats_check is provided by the LebenslaufHeld MCP server (https://lebenslaufheld.de/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on LebenslaufHeld, and thousands of servers like it.
This server
Across the catalogue