clinicaltrials.trials.search

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 80 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/clinicaltrials.trials.search.md

WHAT IT DOES

What clinicaltrials.trials.search does on Apibase

AI agents call clinicaltrials.trials.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.

RISK

Why clinicaltrials.trials.search is rated Low

Read-only search of public clinical trial registry data with no side effects.

From the tool's definition Search 400K+ clinical trials... Returns NCT ID, title, status

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clinicaltrials.trials.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 clinicaltrials.trials.search, this is the rule to start with:

clinicaltrials.trials.search Allowed

clinicaltrials.trials.search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clinicaltrials.trials.search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every clinicaltrials.trials.search call is checked against it from then on.

FAQ

Questions about clinicaltrials.trials.search

What does the clinicaltrials.trials.search tool do? +

Search 400K+ clinical trials registered on ClinicalTrials.gov by condition, drug/intervention, sponsor, or keyword. Optionally filter by status (RECRUITING, COMPLETED, etc.) and phase (PHASE1–PHASE4). Returns NCT ID, title, status, phases, conditions, sponsor, enrollment, and start/completion dates. Supports pagination via page_token. Data from NIH US Gov (public domain). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does clinicaltrials.trials.search accept? +

clinicaltrials.trials.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.

How do I enforce a policy on clinicaltrials.trials.search? +

Register the Apibase MCP server in PolicyLayer and add a rule for clinicaltrials.trials.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.

What risk level is clinicaltrials.trials.search? +

clinicaltrials.trials.search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit clinicaltrials.trials.search? +

Yes. Add a rate_limit block to the clinicaltrials.trials.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.

How do I block clinicaltrials.trials.search completely? +

Set action: deny in the PolicyLayer policy for clinicaltrials.trials.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.

What MCP server provides clinicaltrials.trials.search? +

clinicaltrials.trials.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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →