AI agents call gesundheits_check to retrieve information from Lokyy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a diagnostic/inspection tool that reads and validates the state of the knowledge base. It produces informational output about the structure without creating, modifying, deleting, or executing anything. The severity is low because misuse would only surface false reports about data integrity, with no risk of data loss, corruption, or external impact.
From the tool's definition The tool performs "Deterministische Strukturprüfung" (deterministic structure checking) of the knowledge base, examining references, indexes, frontmatter, and formats.
Attacks that exploit this kind of access
Deterministische Strukturprüfung der ganzen Wissensbasis (Verweise, Register, Frontmatter, Formate). Eine leere Bilanz ist ein gutes Ergebnis. It is categorised as a Read tool in the Lokyy MCP Server, which means it retrieves data without modifying state.
Register the Lokyy MCP server in PolicyLayer and add a rule for gesundheits_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 Lokyy. Nothing to install.
gesundheits_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 gesundheits_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 gesundheits_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.
gesundheits_check is provided by the Lokyy MCP server (oliverhees/lokyy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →