clinical_trials

SERVERScorpTech x402 API SOURCEhttps://scorptech.it.com/api/x402/mcp

High RISK CLASS

Category Execute

Parameters 90 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-it-scorptech-x402/clinical-trials.md

WHAT IT DOES

What clinical_trials does on ScorpTech x402 API

AI agents invoke clinical_trials to trigger actions in ScorpTech x402 API. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`sort`	string	—	relevance (default), updated, start
`term`	string	—	Other keywords (drug, NCT id, ...). Alias: q
`limit`	integer	—	Studies per page 1-50 (default 10)
`phase`	string	—	Comma list: early1, 1, 2, 3, 4, na
`status`	string	—	Comma list: open, closed, recruiting, not_yet_recruiting, active_not_recruiting, completed, terminated, ...
`sponsor`	string	—	Lead sponsor or collaborator
`location`	string	—	City, state or country
`condition`	string	—	Condition or disease, e.g. type 2 diabetes
`pageToken`	string	—	nextPageToken from a previous response

Parameters from the server's own tool schema.

RISK

Why clinical_trials is rated High

clinical_trials triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clinical_trials safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clinical_trials, this is the rule to start with:

clinical_trials Rate-limited

clinical_trials stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clinical_trials": {
      "limits": [
        {
          "counter": "clinical_trials_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every clinical_trials call is checked against it from then on.

FAQ

Questions about clinical_trials

What does the clinical_trials tool do? +

Search ClinicalTrials.gov (API v2) by condition, keyword, location, sponsor, recruitment status (or open/closed) and phase. Returns NCT id, title, status, phases, study type, conditions, interventions, lead sponsor, start and completion dates, enrollment, results flag, a short summary and up to 5 sites (ranked by your location), with total count and a page token. Informational only, not medical advice. Price: $0.02 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/clinical-trials. It is categorised as a Execute tool in the ScorpTech x402 API MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does clinical_trials accept? +

clinical_trials accepts 9 parameters: sort, term, limit, phase, status, sponsor, location, condition, pageToken. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on clinical_trials? +

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

What risk level is clinical_trials? +

clinical_trials is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit clinical_trials? +

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

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

clinical_trials is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScorpTech x402 API, and thousands of servers like it.

This server

All 1012 ScorpTech x402 API tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →