clinical_site_selector

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

High RISK CLASS

Category Execute

Parameters 41 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/clinical-site-selector.md

WHAT IT DOES

What clinical_site_selector does on Livedatalink

AI agents invoke clinical_site_selector to trigger actions in Livedatalink. 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
`city`	string	—	Optional city to further localize the trial-location and provider search (e.g. 'Houston'); use with state.
`state`	string	—	Optional 2-letter US state to scope trial and provider counts (e.g. 'TX'). Omit for a national read.
`condition`	string	Yes	Medical condition / disease to evaluate (e.g. 'melanoma', 'type 2 diabetes', 'Alzheimer disease').
`specialty`	string	—	Optional NPPES specialty taxonomy keyword to override the condition-to-specialty mapping (e.g. 'Cardiology', 'Endocrinology').

Parameters from the server's own tool schema.

RISK

Why clinical_site_selector is rated High

clinical_site_selector 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_site_selector 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 clinical_site_selector, this is the rule to start with:

clinical_site_selector Rate-limited

clinical_site_selector 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_site_selector": {
      "limits": [
        {
          "counter": "clinical_site_selector_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 Livedatalink, apply this rule, and every clinical_site_selector call is checked against it from then on.

FAQ

Questions about clinical_site_selector

What does the clinical_site_selector tool do? +

One-call clinical-trial-activity + local-specialist-availability read for a medical condition in a US geography - the question a trial sponsor, CRO, or site-feasibility analyst asks before choosing where to run a study. Joins three keyless public sources: ClinicalTrials.gov (exact count of RECRUITING trials for the condition, scoped to the geography and compared to the national total, plus the top lead sponsors and phase mix from the recruiting sample), the NPPES NPI Registry (local specialist availability - how many providers carry a specialty taxonomy relevant to the condition in the area, across physicians and NPs/PAs/pharmacists/RNs in the field), and optionally US Census ACS population context for the state (needs a Census key; degrades gracefully). The condition is mapped to a provider specialty heuristically; pass an explicit 'specialty' to override. Returns a readable brief with a headline banding trial activity (HIGH/MODERATE/LOW/NONE) and specialist availability. A source that fails is noted, not fatal. INFORMATIONAL research / site-feasibility synthesis, NOT medical advice or a directive to enroll in any trial. It is categorised as a Execute tool in the Livedatalink MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does clinical_site_selector accept? +

clinical_site_selector accepts 4 parameters: city, state, condition, specialty. Required: condition. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on clinical_site_selector? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for clinical_site_selector: 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.

What risk level is clinical_site_selector? +

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

Can I rate-limit clinical_site_selector? +

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

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

clinical_site_selector 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.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 280 Livedatalink 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 →