# get_research_paper

Fetch a single research paper by its internal id or PubMed id.

Agent View of the PolicyLayer registry record for `get_research_paper`. HTML page: https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/get-research-paper

## Facts

- Tool: `get_research_paper`
- Server: Cure Cancer With AI (`https://www.curecancerwithai.com/api/mcp`) — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai.md
- Homepage: https://github.com/hifarrer/ccwai-api
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `idOrPubmedId` | string | yes | Internal id or PubMed id, e.g. "38123456". |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_research_paper",
    "arguments": {
      "idOrPubmedId": "<idOrPubmedId>"
    }
  }
}
```

## Why get_research_paper is rated Low

This tool retrieves existing research paper metadata or content from a database. No data is created, modified, deleted, or executed. It is a straightforward query/fetch operation typical of document retrieval systems. The low severity reflects minimal risk even if misused—retrieving research papers poses no security or operational threat.

From the tool's own definition: "Tool description states 'Fetch a single research paper by its internal id or PubMed id.' The verb 'Fetch' and context of retrieving published research papers indicates a read-only data retrieval operation with no side effects or modifications."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Cure Cancer With AI:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_research_paper": {}
  }
}
```

## Other tools on Cure Cancer With AI (14)

- `predict_dti` — Execute — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/predict-dti.md
- `predict_ppi` — Execute — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/predict-ppi.md
- `get_blog_post` — Read — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/get-blog-post.md
- `get_clinical_trial` — Read — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/get-clinical-trial.md
- `list_blog_posts` — Read — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/list-blog-posts.md
- `list_clinical_trials` — Read — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/list-clinical-trials.md
- `list_compound_characteristics` — Read — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/list-compound-characteristics.md
- `list_fda_approvals` — Read — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/list-fda-approvals.md
- `list_news` — Read — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/list-news.md
- `list_research` — Read — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/list-research.md
- `mammal_health` — Read — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/mammal-health.md
- `predict_clintox` — Read — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/predict-clintox.md
- `search_compounds` — Read — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/search-compounds.md
- `search_oncology` — Read — https://policylayer.com/tools/io-github-hifarrer-cure-cancer-with-ai/search-oncology.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-hifarrer-cure-cancer-with-ai · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-hifarrer-cure-cancer-with-ai