disease_getter
AI agents call disease_getter to retrieve information from CzechMedMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name and context within a healthcare information server, 'disease_getter' most likely retrieves or queries disease data from Czech healthcare databases (SUKL, MKN-10, etc.) without side effects. The empty description reduces confidence, but the semantic pattern matches read operations common in medical reference tools.
From the tool's definition Tool name 'disease_getter' indicates retrieval of disease information. Description is empty, limiting precision, but naming convention and context among sibling tools (article_getter, article_searcher, czechmed_browse_diagnosis, czechmed_diagnosis_assist)…
Attacks that exploit this kind of access
disease_getter. It is categorised as a Read tool in the CzechMedMCP MCP Server, which means it retrieves data without modifying state.
Register the CzechMed MCP server in PolicyLayer and add a rule for disease_getter: 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 CzechMedMCP. Nothing to install.
disease_getter 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 disease_getter 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 disease_getter. 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.
disease_getter is provided by the CzechMed MCP server (petrsovadina/czechmedmcp). 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 →