clinicaltrials.trials.detail
Retrieve full details of a specific clinical trial by its NCT identifier (e.g. "NCT04368728"). Returns title, official title, status, sponsor, conditions, interventions, design info, enrollment, eligibility criteria (age/sex/health volunteer), primary and secondary outcomes, brief summary, and up...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/clinicaltrials.trials.detail.md
What clinicaltrials.trials.detail does on Apibase
AI agents call clinicaltrials.trials.detail 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 |
|---|---|---|---|
nct_id | string | Yes | ClinicalTrials.gov registry identifier in NCT format (e.g. "NCT04368728", "NCT01454700"). Must start with "NCT" followed by 8 digits. |
Parameters from the server's own tool schema.
Why clinicaltrials.trials.detail is rated Low
Tool queries public clinical trial data without modification or side effects; no destructive or financial operations possible.
From the tool's definition Retrieve full details of a specific clinical trial by NCT identifier
Attacks that exploit this kind of access
The rule that runs clinicaltrials.trials.detail 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.detail, this is the rule to start with:
clinicaltrials.trials.detail 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 clinicaltrials.trials.detail call is checked against it from then on.
Questions about clinicaltrials.trials.detail
Retrieve full details of a specific clinical trial by its NCT identifier (e.g. "NCT04368728"). Returns title, official title, status, sponsor, conditions, interventions, design info, enrollment, eligibility criteria (age/sex/health volunteer), primary and secondary outcomes, brief summary, and up to 10 study locations. Source: ClinicalTrials.gov v2 API (NIH, public domain). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
clinicaltrials.trials.detail accepts 1 parameter: nct_id. Required: nct_id. 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 clinicaltrials.trials.detail: 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.
clinicaltrials.trials.detail 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 clinicaltrials.trials.detail 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 clinicaltrials.trials.detail. 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.
clinicaltrials.trials.detail 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