New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

clinicaltrials.trials.recruiting

Find clinical trials currently open for enrollment (status=RECRUITING) for a given condition or drug. Optionally filter by phase (e.g. PHASE3 for large confirmatory trials). Returns NCT ID, title, phases, conditions, sponsor, enrollment target, and start/completion dates. Useful for patients or r...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 40 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.recruiting.md

What clinicaltrials.trials.recruiting does on Apibase

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

ParameterTypeRequiredDescription
limit integer — Maximum number of recruiting trials to return (1–50). Default: 10.
phase string — Restrict to a specific trial phase among recruiting studies. PHASE3 = large confirmatory trials; PHASE1 = early safety studies.
condition string — Disease or condition to search for among currently recruiting trials (e.g. "lung cancer", "Alzheimer", "type 2 diabetes").
intervention string — Drug or intervention to search for among recruiting trials (e.g. "pembrolizumab", "mRNA vaccine", "gene therapy").

Parameters from the server's own tool schema.

Why clinicaltrials.trials.recruiting is rated Low

Retrieves public clinical trial data from ClinicalTrials.gov with no side effects.

From the tool's definition Find clinical trials currently open for enrollment... Returns NCT ID, title

Questions about clinicaltrials.trials.recruiting

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

Find clinical trials currently open for enrollment (status=RECRUITING) for a given condition or drug. Optionally filter by phase (e.g. PHASE3 for large confirmatory trials). Returns NCT ID, title, phases, conditions, sponsor, enrollment target, and start/completion dates. Useful for patients or researchers seeking open studies. Source: ClinicalTrials.gov v2 (NIH, 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.recruiting accept? +

clinicaltrials.trials.recruiting accepts 4 parameters: limit, phase, condition, 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.recruiting? +

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

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

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

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

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.