research_paper_qa
Synthèse littérature scientifique (PaperQA2) — Gapup agent-payable C-suite expertise (RISK). Returns a structured, audited deliverable. Answers: Conduct a literature review on <topic> — what does the evidence show across recent papers? · Evaluate the current hypothesis that <claim> — supporting a...
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/research-paper-qa.md
What research_paper_qa does on Mcp Knowledge
AI agents call research_paper_qa 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 |
max_papers | integer | Yes | |
year_range | object | — | |
focus_domain | string | Yes | |
include_preprints | boolean | Yes | |
research_question | string | Yes | |
evidence_grade_required | string | Yes |
Parameters from the server's own tool schema.
Why research_paper_qa is rated Low
This tool retrieves and synthesizes scientific literature. All described actions (literature review, hypothesis evaluation, contradiction mapping, state-of-the-art assessment) are read/query operations on existing published research. No data is created, modified, deleted, or executed.
From the tool's definition Synthèse littérature scientifique (PaperQA2) — literature review, evaluate hypothesis, map contradictions, state-of-the-art understanding, interdisciplinary synthesis
Attacks that exploit this kind of access
The rule that runs research_paper_qa 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 research_paper_qa, this is the rule to start with:
research_paper_qa 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 research_paper_qa call is checked against it from then on.
Questions about research_paper_qa
Synthèse littérature scientifique (PaperQA2) — Gapup agent-payable C-suite expertise (RISK). Returns a structured, audited deliverable. Answers: Conduct a literature review on <topic> — what does the evidence show across recent papers? · Evaluate the current hypothesis that <claim> — supporting and contradicting evidence with citations. · Map contradictions in the literature on <topic> — which camps exist, how many papers per side? · What is the state-of-the-art understanding of <phenomenon> as of <year>? · Perform an interdisciplinary synthesis on <topic> — findings from <domain A> and <domain B>. Reference case: Gut-brain axis · Cognitive performance in healthy adults · OpenAlex+SemanticScholar+CORE · Evidence synthesis · DOI-verified citations · Contradictions + gaps mapped. 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.
research_paper_qa accepts 7 parameters: async, max_papers, year_range, focus_domain, include_preprints, research_question, evidence_grade_required. Required: max_papers, focus_domain, include_preprints, research_question, evidence_grade_required. 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 research_paper_qa: 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.
research_paper_qa 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 research_paper_qa 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 research_paper_qa. 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.
research_paper_qa 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