Retrieves a single clinical trial with search field parameters.
AI agents call get_clinical_trials_by_id 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 retrieves clinical trial information using an ID-based lookup. The verb 'retrieves' and the absence of any modification, deletion, or execution language confirm this is a Read operation. There are no side effects—only data retrieval. Severity is low because retrieving clinical trial metadata poses minimal risk even if misused by an LLM agent.
From the tool's definition Tool name 'get_clinical_trials_by_id' and description 'Retrieves a single clinical trial with search field parameters' indicate a read-only query operation that fetches data without modification.
Attacks that exploit this kind of access
Retrieves a single clinical trial with search field parameters. 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_clinical_trials_by_id: 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_clinical_trials_by_id 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_clinical_trials_by_id 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_clinical_trials_by_id. 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_clinical_trials_by_id 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 →