czechmed_get_diagnosis_stats
AI agents call czechmed_get_diagnosis_stats 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.
Despite the empty description reducing confidence slightly, the tool name strongly suggests a data retrieval operation ('get') focused on diagnosis statistics from Czech healthcare databases. This aligns with other sibling tools like 'czechmed_browse_diagnosis' which are clearly informational. No modification, deletion, execution, or financial action is implied.
From the tool's definition Tool name 'czechmed_get_diagnosis_stats' indicates retrieval of statistical data about diagnoses. The 'get_' prefix and 'stats' suffix are characteristic of read operations that query and retrieve information without modification.
Attacks that exploit this kind of access
czechmed_get_diagnosis_stats. 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_get_diagnosis_stats: 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_get_diagnosis_stats 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_get_diagnosis_stats 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_get_diagnosis_stats. 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_get_diagnosis_stats 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 →