paper_health
检查论文下载服务各数据源的可用性（Unpaywall、arXiv、Sci-Hub 镜像）。
This record as markdown: /tools/45645678a-scholar-mcp/paper-health.md
What paper_health does on Scholar MCP Server
AI agents call paper_health 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.
Why paper_health is rated Low
This is a diagnostic/monitoring tool that queries the operational status of external academic data sources. It performs a read-only health check operation with no side effects, no data retrieval for the user, no modifications, and no external state changes beyond a simple availability probe. Low severity because even misuse cannot harm data or systems—it can only report status information.
From the tool's definition Tool description states it 'checks the availability' (检查可用性) of paper download data sources (Unpaywall, arXiv, Sci-Hub mirrors). The verb 'check' and 'availability' indicate status monitoring or health checking operations without modifying any data.
Attacks that exploit this kind of access
The rule that runs paper_health safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Scholar MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For paper_health, this is the rule to start with:
paper_health 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 Scholar MCP Server, apply this rule, and every paper_health call is checked against it from then on.
Questions about paper_health
检查论文下载服务各数据源的可用性（Unpaywall、arXiv、Sci-Hub 镜像）。. It is categorised as a Read tool in the Scholar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Scholar MCP Server MCP server in PolicyLayer and add a rule for paper_health: 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 Scholar MCP Server. Nothing to install.
paper_health 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 paper_health 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 paper_health. 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.
paper_health is provided by the Scholar MCP Server MCP server (45645678a/scholar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Scholar MCP Server, and thousands of servers like it.
This server
Across the catalogue