health.clinical.study
Full details for a clinical trial by NCT ID — protocol, conditions, interventions with dosing, eligibility criteria (age, sex), primary/secondary outcomes, sponsor, enrollment, phase, study design, dates, results if available (ClinicalTrials.gov)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/health.clinical.study.md
What health.clinical.study does on Apibase
AI agents call health.clinical.study 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 health.clinical.study is rated Low
Retrieves published clinical trial metadata from ClinicalTrials.gov; no side effects or data modification.
From the tool's definition Full details for a clinical trial by NCT ID — protocol, conditions, interventions
Attacks that exploit this kind of access
The rule that runs health.clinical.study 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.study, this is the rule to start with:
health.clinical.study 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.study call is checked against it from then on.
Questions about health.clinical.study
Full details for a clinical trial by NCT ID — protocol, conditions, interventions with dosing, eligibility criteria (age, sex), primary/secondary outcomes, sponsor, enrollment, phase, study design, dates, results if available (ClinicalTrials.gov). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
health.clinical.study 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 health.clinical.study: 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.study 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.study 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.study. 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.study 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