Low Risk

clinicaltrials_search_studies

Search for clinical trial studies from ClinicalTrials.gov. Supports full-text and field-specific queries, status/phase/geographic filters, pagination, sorting, and field selection. Use the fields parameter to reduce payload size — full study records are ~70KB each.

Risk signalsAccepts freeform code/query input (query) · High parameter count (17 properties)

Part of the Clinicaltrialsgov server.

clinicaltrials_search_studies is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE CLINICALTRIALSGOV →

Free to start. No card required.

AI agents call clinicaltrials_search_studies to retrieve information from Clinicaltrialsgov 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 clinicaltrials_search_studies 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.

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

See the full Clinicaltrialsgov policy for all 7 tools.

Get this rule live on your own Clinicaltrialsgov server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CLINICALTRIALSGOV →

These attack patterns abuse exactly the kind of access clinicaltrials_search_studies gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so clinicaltrials_search_studies only ever does what you allow.

SECURE CLINICALTRIALSGOV →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the clinicaltrials_search_studies tool do? +

Search for clinical trial studies from ClinicalTrials.gov. Supports full-text and field-specific queries, status/phase/geographic filters, pagination, sorting, and field selection. Use the fields parameter to reduce payload size — full study records are ~70KB each.. It is categorised as a Read tool in the Clinicaltrialsgov MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on clinicaltrials_search_studies? +

Register the Clinicaltrialsgov MCP server in PolicyLayer and add a rule for clinicaltrials_search_studies: 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 Clinicaltrialsgov. Nothing to install.

What risk level is clinicaltrials_search_studies? +

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

Can I rate-limit clinicaltrials_search_studies? +

Yes. Add a rate_limit block to the clinicaltrials_search_studies 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 clinicaltrials_search_studies completely? +

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

clinicaltrials_search_studies is provided by the Clinicaltrialsgov MCP server (cyanheads/clinicaltrialsgov-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 Clinicaltrialsgov tool call.

Deterministic rules across all 7 Clinicaltrialsgov tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.