# paper_translate

A read tool on the Scholar MCP Server MCP server.

Agent View of the PolicyLayer registry record for `paper_translate`. HTML page: https://policylayer.com/tools/45645678a-scholar-mcp/paper-translate

## Facts

- Tool: `paper_translate`
- Server: Scholar MCP Server (`45645678a/scholar-mcp`) — https://policylayer.com/tools/45645678a-scholar-mcp.md
- Homepage: https://github.com/45645678a/scholar-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "paper_translate",
    "arguments": {}
  }
}
```

## Why paper_translate is rated Low

Based on context from sibling tools (paper_search, paper_download, paper_analyze) and the server's focus on academic research, 'paper_translate' most likely retrieves and transforms existing paper text into other languages without modifying source data or triggering external actions with unpredictable side effects. This is consistent with Read operations.

From the tool's own definition: "Tool name 'paper_translate' combined with server description indicating academic paper analysis capabilities suggests this tool translates research paper content. No description provided, limiting certainty."

## Use case

AI agents call paper_translate to retrieve information from Scholar MCP Server 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 Scholar MCP Server:

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

## Other tools on Scholar MCP Server (7)

- `paper_ai_analyze` — Read — https://policylayer.com/tools/45645678a-scholar-mcp/paper-ai-analyze.md
- `paper_citation_graph` — Read — https://policylayer.com/tools/45645678a-scholar-mcp/paper-citation-graph.md
- `paper_download` — Read — https://policylayer.com/tools/45645678a-scholar-mcp/paper-download.md
- `paper_health` — Read — https://policylayer.com/tools/45645678a-scholar-mcp/paper-health.md
- `paper_recommend` — Read — https://policylayer.com/tools/45645678a-scholar-mcp/paper-recommend.md
- `paper_search` — Read — https://policylayer.com/tools/45645678a-scholar-mcp/paper-search.md
- `paper_batch_download` — Write — https://policylayer.com/tools/45645678a-scholar-mcp/paper-batch-download.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=45645678a-scholar-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/45645678a-scholar-mcp