list_clinical_trials
List clinical trials from public registries (conditions, status, intervention type). Filter by condition, status (e.g. RECRUITING), or keyword.
This record as markdown: /tools/io-github-hifarrer-cure-cancer-with-ai/list-clinical-trials.md
What list_clinical_trials does on Cure Cancer With AI
AI agents call list_clinical_trials 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 |
|---|---|---|---|
limit | integer | — | Results per page (1–100, default 20). |
offset | integer | — | Number of results to skip (default 0). |
search | string | — | Keyword search across title and description. |
status | string | — | Filter by trial status, e.g. RECRUITING. |
condition | string | — | Filter by condition. |
Parameters from the server's own tool schema.
Why list_clinical_trials is rated Low
This tool retrieves and filters publicly available clinical trial information from established registries. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. The operation is read-only and informational in nature, making it a Read category tool with low severity.
From the tool's definition Tool name is 'list_clinical_trials' and description states it 'List[s] clinical trials from public registries' with filtering capability. No modification, deletion, or execution is performed—only retrieval and querying of publicly available data.
Attacks that exploit this kind of access
The rule that runs list_clinical_trials 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 list_clinical_trials, this is the rule to start with:
list_clinical_trials 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 list_clinical_trials call is checked against it from then on.
Questions about list_clinical_trials
List clinical trials from public registries (conditions, status, intervention type). Filter by condition, status (e.g. RECRUITING), or keyword. It is categorised as a Read tool in the Cure Cancer With AI MCP Server, which means it retrieves data without modifying state.
list_clinical_trials accepts 5 parameters: limit, offset, search, status, condition. 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 list_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 Cure Cancer With AI. Nothing to install.
list_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 list_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 list_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.
list_clinical_trials 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