clinical_evidence_briefer
Brief évidence clinique (GRADE) — Gapup agent-payable C-suite expertise (RISK). Returns a structured, audited deliverable. Answers: Review the clinical evidence for <drug/intervention> in <indication> — GRADE rating, key trials, safety signals. · Scan safety signals for <molecule> in <population>...
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/clinical-evidence-briefer.md
What clinical_evidence_briefer does on Mcp Knowledge
AI agents call clinical_evidence_briefer 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 |
|---|---|---|---|
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 |
topic | string | Yes | |
max_studies | integer | Yes | |
intervention | string | — | |
evidence_focus | string | Yes | |
target_disease | string | — | |
date_range_years | integer | Yes | |
intervention_type | string | — |
Parameters from the server's own tool schema.
Why clinical_evidence_briefer is rated Low
The tool retrieves and summarizes existing clinical evidence, GRADE ratings, trial data, safety signals from FAERS, and comparative effectiveness information. All described operations are read/query operations — fetching and structuring existing data. No writes, executions, or financial transactions are involved.
From the tool's definition Brief évidence clinique (GRADE)... Returns a structured, audited deliverable... Review the clinical evidence... Scan safety signals... Assess comparative effectiveness... Is there evidence supporting drug repurposing
Attacks that exploit this kind of access
The rule that runs clinical_evidence_briefer 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_evidence_briefer, this is the rule to start with:
clinical_evidence_briefer is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every clinical_evidence_briefer call is checked against it from then on.
Questions about clinical_evidence_briefer
Brief évidence clinique (GRADE) — Gapup agent-payable C-suite expertise (RISK). Returns a structured, audited deliverable. Answers: Review the clinical evidence for <drug/intervention> in <indication> — GRADE rating, key trials, safety signals. · Scan safety signals for <molecule> in <population> — adverse events, severity, frequency from FAERS and trial data. · Assess comparative effectiveness of <intervention> versus <comparator> for <disease> — what does the evidence show? · Is there evidence supporting drug repurposing of <molecule> for <new indication> — existing trials and GRADE quality? · What are the evidence gaps for <intervention> in <patient population> before formulary adoption? Reference case: Semaglutide 2.4mg · Chronic weight management in non-diabetic adults · GRADE high efficacy · studies found · nausea/GI signals · FDA approved · PubMed+ClinicalTrials+OpenFDA. Inputs are validated server-side — send the documented case fields. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
clinical_evidence_briefer accepts 8 parameters: async, topic, max_studies, intervention, evidence_focus, target_disease, date_range_years, intervention_type. Required: topic, max_studies, evidence_focus, date_range_years. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for clinical_evidence_briefer: 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.
clinical_evidence_briefer is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the clinical_evidence_briefer 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.
Set action: deny in the PolicyLayer policy for clinical_evidence_briefer. 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.
clinical_evidence_briefer 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.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue