Check EU Directive 2023/970 deadlines by headcount (Art. 4, 7, 16). Sprawdza terminy Dyrektywy UE 2023/970 według liczby pracowników.
AI agents call check_deadline to retrieve information from Gaproll without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
country | string | — | |
employee_count | integer | — |
Parameters from the server's own tool schema.
This tool retrieves or queries compliance deadline information deterministically based on employer headcount thresholds defined in EU Directive 2023/970. It is a pure read operation with no side effects—it does not create, modify, delete, execute code, or commit financial obligations. The blast radius of misuse is minimal (an agent might retrieve incorrect deadline information, but no systems are modified or harmed).
From the tool's definition Tool name 'check_deadline' and description 'Check EU Directive 2023/970 deadlines by headcount' indicate a retrieval operation that queries deadline information based on input parameters (headcount).
Documented attack patterns abuse exactly the kind of access check_deadline gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gaproll, and nothing reaches the server without passing your rules. This is the rule we recommend for check_deadline:
{
"version": "1",
"default": "deny",
"tools": {
"check_deadline": {}
}
}check_deadline is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check EU Directive 2023/970 deadlines by headcount (Art. 4, 7, 16). Sprawdza terminy Dyrektywy UE 2023/970 według liczby pracowników. It is categorised as a Read tool in the Gaproll MCP Server, which means it retrieves data without modifying state.
check_deadline accepts 2 parameters: country, employee_count. The full parameter table on this page comes from the server's own tool schema.
Register the Gaproll MCP server in PolicyLayer and add a rule for check_deadline: 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 Gaproll. Nothing to install.
check_deadline 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 check_deadline 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 check_deadline. 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.
check_deadline is provided by the Gaproll MCP server (bartek-ywte/gaproll). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gaproll, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Gaproll tools catalogued and risk-classified — across an index of 43,000+ MCP servers.