Retrieves clinical trials that match a patient
AI agents call get_matching_clinical_trials to retrieve information from Cardiovascular Disease without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs information retrieval only. It searches and returns clinical trial data relevant to a patient's profile but does not create, modify, delete, or execute any operations. The worst-case misuse (returning incorrect trial matches) has minimal blast radius compared to tools that could modify patient records or execute external actions. Classification as Read is appropriate.
From the tool's definition Tool description states it 'Retrieves clinical trials that match a patient' — a query/lookup operation with no modification, deletion, or execution of external systems.
Attacks that exploit this kind of access
Retrieves clinical trials that match a patient. It is categorised as a Read tool in the Cardiovascular Disease MCP Server, which means it retrieves data without modifying state.
Register the Cardiovascular Disease MCP server in PolicyLayer and add a rule for get_matching_clinical_trials: 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 Cardiovascular Disease. Nothing to install.
get_matching_clinical_trials 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 get_matching_clinical_trials 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 get_matching_clinical_trials. 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.
get_matching_clinical_trials is provided by the Cardiovascular Disease MCP server (jamesvdinh/cardiovascular-disease-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 →