Complete drug profile: registration + availability + reimbursement + evidence.
AI agents call czechmed_drug_profile 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 tool aggregates and presents existing drug information from Czech healthcare registries (SUKL, NRPZS) and biomedical sources. It performs pure data retrieval with no side effects, no code execution, no deletions, and no financial transactions. The worst plausible misuse is returning incomplete or outdated drug information, which poses low risk.
From the tool's definition Tool retrieves 'drug profile' data including 'registration + availability + reimbursement + evidence' — all informational attributes that are queried from healthcare databases without modification or action.
Attacks that exploit this kind of access
Complete drug profile: registration + availability + reimbursement + evidence. 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_drug_profile: 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_drug_profile 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_drug_profile 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_drug_profile. 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_drug_profile 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 →