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-gapup-mcp/research-paper-qa.md
What research_paper_qa does on Gapup Mcp
AI agents call research_paper_qa to retrieve information from Gapup Mcp 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 performs scientific literature review and synthesis, retrieving and summarizing existing research papers. It queries and reads academic content without modifying, executing, or financially transacting anything. The 'agent-payable' note on the server implies a per-call cost, but the tool itself is a read/query operation. Severity is low as misuse would at worst produce misleading summaries.
From the tool's definition Synthèse littérature scientifique (PaperQA2) — Returns a structured, audited deliverable. Answers: Conduct a literature review on <topic> — what does the evidence show across recent papers?
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 Gapup Mcp, 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 Gapup Mcp, 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 Gapup Mcp 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 Gapup 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 Gapup Mcp. 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 Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
This server
Across the catalogue