Get comprehensive details for a single clinical trial. This tool retrieves detailed information for a single clinical trial given its NCT ID. Input: - `nct_id`: The NCT ID of the trial to retrieve. Example: `'NCT04280705'` - `fields`: A list of specific fields to return. If no...
Single-target operation
Part of the Clinical Trials Data Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_trial_details to retrieve information from Clinical Trials Data Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_trial_details only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_trial_details:
rules:
- action: allowSee the full Clinical Trials Data Server policy for all 12 tools.
Agents calling read-class tools like get_trial_details have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get comprehensive details for a single clinical trial. This tool retrieves detailed information for a single clinical trial given its NCT ID. Input: - `nct_id`: The NCT ID of the trial to retrieve. Example: `'NCT04280705'` - `fields`: A list of specific fields to return. If not provided, returns DETAIL_TOOL_DEFAULTS (25 comprehensive fields covering: NCTId, BriefTitle, OfficialTitle, Acronym, Condition, Keyword, Phase, OverallStatus, InterventionType, InterventionName, InterventionDescription, ArmGroupLabel, ArmGroupType, ArmGroupDescription, EligibilityCriteria, MinimumAge, MaximumAge, Sex, PrimaryOutcomeMeasure, SecondaryOutcomeMeasure, BriefSummary, LocationFacility, LocationCountry, LeadSponsorName, CollaboratorName, HasResults).. It is categorised as a Read tool in the Clinical Trials Data Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_trial_details. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Clinical Trials Data Server MCP server.
get_trial_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 get_trial_details rule in your Intercept 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 Intercept policy for get_trial_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.
get_trial_details is provided by the Clinical Trials Data Server MCP server (plainyogurt21/clintrials-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept