trials_details
Get full detail for one clinical trial by its NCT id (e.g. 'NCT02562313'): title, status, conditions, sponsor, phase, interventions, brief summary, enrollment, start/completion dates, number of sites, and the study URL.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/trials-details.md
What trials_details does on Livedatalink
AI agents call trials_details to retrieve information from Livedatalink 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 NCT id, e.g. 'NCT02562313'. |
Parameters from the server's own tool schema.
Why trials_details is rated Low
This tool retrieves publicly available clinical trial information by ID. It has no side effects, makes no modifications, and only queries/returns data. Blast radius is minimal — worst case is an agent consuming API quota or retrieving sensitive trial info.
From the tool's definition 'Get full detail for one clinical trial by its NCT id': title, status, conditions, sponsor, phase, interventions, brief summary, enrollment, start/completion dates, number of sites, and the study URL
Attacks that exploit this kind of access
The rule that runs trials_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For trials_details, this is the rule to start with:
trials_details 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 Livedatalink, apply this rule, and every trials_details call is checked against it from then on.
Questions about trials_details
Get full detail for one clinical trial by its NCT id (e.g. 'NCT02562313'): title, status, conditions, sponsor, phase, interventions, brief summary, enrollment, start/completion dates, number of sites, and the study URL. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
trials_details 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 Livedatalink MCP server in PolicyLayer and add a rule for trials_details: 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 Livedatalink. Nothing to install.
trials_details 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 trials_details 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 trials_details. 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.
trials_details is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue