Low Risk

get_full_study_details

Get detailed information about a specific clinical trial

How to control get_full_study_details ↓

What get_full_study_details does on ClinicalTrials MCP Server

AI agents call get_full_study_details to retrieve information from ClinicalTrials MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_full_study_details needs a policy

This tool performs a query/retrieval operation on clinical trial data without side effects. It accesses publicly available metadata from ClinicalTrials.gov. The action is informational only—retrieving structured data about trials—which is characteristic of Read operations. There is no capability to modify, delete, execute code, or interact with financial systems.

From the tool's definition The tool 'get_full_study_details' retrieves detailed information about a specific clinical trial. The server description emphasizes 'search and access clinical trial data' and 'retrieving detailed trial metadata by NCT ID', indicating read-only access to…

Documented attack patterns abuse exactly the kind of access get_full_study_details gives an agent:

How to control get_full_study_details

PolicyLayer is an MCP gateway — it sits between your AI agents and ClinicalTrials MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_full_study_details:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_full_study_details": {}
  }
}

get_full_study_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register ClinicalTrials MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_full_study_details

What does the get_full_study_details tool do? +

Get detailed information about a specific clinical trial. It is categorised as a Read tool in the ClinicalTrials MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_full_study_details? +

Register the ClinicalTrials MCP Server MCP server in PolicyLayer and add a rule for get_full_study_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 ClinicalTrials MCP Server. Nothing to install.

What risk level is get_full_study_details? +

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

Can I rate-limit get_full_study_details? +

Yes. Add a rate_limit block to the get_full_study_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.

How do I block get_full_study_details completely? +

Set action: deny in the PolicyLayer policy for get_full_study_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.

What MCP server provides get_full_study_details? +

get_full_study_details is provided by the ClinicalTrials MCP Server MCP server (jackkuo666/clinicaltrials-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ClinicalTrials MCP Server tool call.

Start from ClinicalTrials MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

7 ClinicalTrials MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.