Search Czech ICD-10 (MKN-10) diagnoses.
AI agents call czechmed_search_diagnosis 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.
This is a pure read operation that queries a standardized medical classification system (Czech ICD-10). It does not create, modify, delete, or execute any actions—it simply retrieves diagnostic information. The blast radius of misuse is minimal: an AI agent could only retrieve irrelevant diagnostic codes, which would not cause harm. Classified as Read with low severity.
From the tool's definition The tool "search" diagnoses in a medical classification database (MKN-10/ICD-10). This retrieves or queries existing diagnostic codes with no modification capability or side effects.
Attacks that exploit this kind of access
Search Czech ICD-10 (MKN-10) diagnoses. 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 czechmed_search_diagnosis: 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.
czechmed_search_diagnosis 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 czechmed_search_diagnosis 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 czechmed_search_diagnosis. 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.
czechmed_search_diagnosis 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 →