health.clinical.search
Search 577,000+ clinical trials worldwide — filter by condition (cancer, diabetes), intervention (drug name), sponsor, status (recruiting/completed), phase. Returns NCT ID, title, status, conditions, interventions, sponsor, enrollment. US National Library of Medicine (ClinicalTrials.gov)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/health.clinical.search.md
What health.clinical.search does on Apibase
AI agents call health.clinical.search to retrieve information from Apibase 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 | — | Maximum number of results to return (1–50). Default: 10. |
phase | string | — | Filter by clinical trial phase. PHASE1=safety, PHASE2=efficacy, PHASE3=confirmatory, PHASE4=post-market, NA=not applicable (e.g. observational studies). |
status | string | — | Filter by overall trial status. Most useful values: "RECRUITING" (open enrollment), "COMPLETED" (finished), "ACTIVE_NOT_RECRUITING" (ongoing but closed to new p |
keyword | string | — | Free-text keyword search across all text fields of the trial record (e.g. "immunotherapy", "biomarker", "phase 3 randomized"). |
sponsor | string | — | Sponsor or organization name to search for (e.g. "Pfizer", "NIH", "Mayo Clinic"). Searches the lead sponsor field. |
condition | string | — | Disease or condition to search for (e.g. "diabetes", "breast cancer", "COVID-19"). Searches the conditions field of registered trials. |
page_token | string | — | Pagination token from a previous search response (next_page_token field). Omit for the first page. |
intervention | string | — | Drug or intervention to search for (e.g. "aspirin", "metformin", "CAR T-cell therapy"). Searches the interventions field of registered trials. |
Parameters from the server's own tool schema.
Why health.clinical.search is rated Low
Read-only search of public clinical trial registry metadata with no side effects or data modification capabilities.
From the tool's definition Search clinical trials — filter, returns metadata (NCT ID, title, status, conditions, interventions, sponsor, enrollment)
Attacks that exploit this kind of access
The rule that runs health.clinical.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For health.clinical.search, this is the rule to start with:
health.clinical.search 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 Apibase, apply this rule, and every health.clinical.search call is checked against it from then on.
Questions about health.clinical.search
Search 577,000+ clinical trials worldwide — filter by condition (cancer, diabetes), intervention (drug name), sponsor, status (recruiting/completed), phase. Returns NCT ID, title, status, conditions, interventions, sponsor, enrollment. US National Library of Medicine (ClinicalTrials.gov). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
health.clinical.search accepts 8 parameters: limit, phase, status, keyword, sponsor, condition, page_token, intervention. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for health.clinical.search: 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 Apibase. Nothing to install.
health.clinical.search 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 health.clinical.search 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 health.clinical.search. 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.
health.clinical.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue