clinical_pharma_intel

SERVERMcp Knowledge SOURCEhttps://mcp.gapup.io

Low RISK CLASS

Category Read

Parameters 71 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-mcp-knowledge/clinical-pharma-intel.md

WHAT IT DOES

What clinical_pharma_intel does on Mcp Knowledge

AI agents call clinical_pharma_intel to retrieve information from Mcp Knowledge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`mode`	string	—	Analysis mode. Default "trials". trials=clinical trials, pipeline=sponsor overview, approvals=FDA approvals, recalls=enforcement, adverse_events=FAERS
`async`	boolean	—	If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti
`phase`	string	—	Filter trials by phase (1/2/3/4/NA). Only applies to modes trials and pipeline.
`query`	string	Yes	Drug name, indication, sponsor or molecule (e.g. "atezolizumab", "metastatic NSCLC", "Roche", "semaglutide")
`country`	string	—	ISO 2-letter country code to filter trial sites (e.g. US, FR, DE).
`max_results`	number	—	Maximum number of results to return. Default 20.
`status_filter`	string	—	Filter trials by status. Only applies to modes trials and pipeline.

Parameters from the server's own tool schema.

RISK

Why clinical_pharma_intel is rated Low

This is a read-only intelligence aggregation tool that queries public healthcare databases and APIs. It retrieves and presents clinical trial information, drug approvals, recalls, and adverse event data—all standard research and analytics operations. There is no capability to modify records, execute code, delete data, or commit financial transactions.

From the tool's definition Tool aggregates and retrieves data across five modes: 'trials' (queries ClinicalTrials.gov and EU CTR), 'pipeline' (queries sponsor data), 'approvals' (queries OpenFDA labels), 'recalls' (queries FDA enforcement data), and 'adverse_events' (queries FAERS…

Risk signalsAccepts freeform code/query input (query)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clinical_pharma_intel safely

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

clinical_pharma_intel Allowed

clinical_pharma_intel is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clinical_pharma_intel": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every clinical_pharma_intel call is checked against it from then on.

FAQ

Questions about clinical_pharma_intel

What does the clinical_pharma_intel tool do? +

Clinical and pharmaceutical intelligence for biotech analysts, healthcare fund managers, pharma BD teams, catalyst-driven hedge funds and health journalists. Aggregates live data across five modes: • trials — active/completed clinical trials (ClinicalTrials.gov v2 + EU CTR in parallel, 450k+ records) • pipeline — full pipeline by sponsor: trial count by phase + top indications • approvals — FDA drug label approvals + mechanism of action (OpenFDA) • recalls — FDA enforcement recalls classified by severity (Class I/II/III) • adverse_events — FAERS aggregated reactions: top 10 reactions + serious% Signal detection (P0/P1/P2): P0 if Class I recall OR trial terminated for safety reason P1 if serious adverse events >30% OR ≥3 recalls in 12 months P2 otherwise (standard monitoring) All sources are public and keyless. Optional env OPENFDA_API_KEY raises daily quota from 1,000 to 120,000 requests. SLA: ≤16s p95 (parallel fetch, 8s budget per source). Cache: 6h trials, 24h approvals, 12h recalls, 6h adverse events. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.

What parameters does clinical_pharma_intel accept? +

clinical_pharma_intel accepts 7 parameters: mode, async, phase, query, country, max_results, status_filter. Required: query. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on clinical_pharma_intel? +

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

What risk level is clinical_pharma_intel? +

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

Can I rate-limit clinical_pharma_intel? +

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

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

clinical_pharma_intel is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Knowledge, and thousands of servers like it.

This server

All 271 Mcp Knowledge tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →