get_clinical_trial
Fetch a single clinical trial by NCT id (or internal id), including eligibility criteria and locations.
This record as markdown: /tools/io-github-hifarrer-cure-cancer-with-ai/get-clinical-trial.md
What get_clinical_trial does on Cure Cancer With AI
AI agents call get_clinical_trial to retrieve information from Cure Cancer With AI without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
nctId | string | Yes | NCT id or internal id, e.g. "NCT01234567". |
Parameters from the server's own tool schema.
Why get_clinical_trial is rated Low
This is a retrietary/query operation that retrieves existing clinical trial metadata. It has no side effects, does not execute code, does not create or modify data, and does not delete or move money. The verb 'Fetch' and the specification of read-only output (eligibility criteria, locations) confirm a Read classification.
From the tool's definition Tool description states 'Fetch a single clinical trial' — retrieves data by identifier (NCT id or internal id) with no indication of modification, deletion, or execution capabilities. Returns structured information: eligibility criteria and locations.
Attacks that exploit this kind of access
The rule that runs get_clinical_trial safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cure Cancer With AI, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_clinical_trial, this is the rule to start with:
get_clinical_trial is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cure Cancer With AI, apply this rule, and every get_clinical_trial call is checked against it from then on.
Questions about get_clinical_trial
Fetch a single clinical trial by NCT id (or internal id), including eligibility criteria and locations. It is categorised as a Read tool in the Cure Cancer With AI MCP Server, which means it retrieves data without modifying state.
get_clinical_trial accepts 1 parameter: nctId. Required: nctId. The full parameter table on this page comes from the server's own tool schema.
Register the Cure Cancer With AI MCP server in PolicyLayer and add a rule for get_clinical_trial: 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 Cure Cancer With AI. Nothing to install.
get_clinical_trial 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_trial 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_trial. 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_trial is provided by the Cure Cancer With AI MCP server (https://www.curecancerwithai.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cure Cancer With AI, and thousands of servers like it.
This server
Across the catalogue