paper_status

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/paper-status.md

WHAT IT DOES

What paper_status does on Livedatalink

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

RISK

Why paper_status is rated Low

This tool retrieves and reports status metrics and catalog information from an academic paper database (OpenAlex) and a local indexed corpus. It performs read-only queries to surface metadata about document availability, indexing statistics, and system state. There are no side effects, no data modification, no irreversible actions, and no code execution.

From the tool's definition Tool name 'paper_status' and description state it 'Report[s]' status information about catalogs, indexed corpus counts, and metadata. Verbs are passive/informational: 'served', 'counts', 'refresh timestamp'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs paper_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For paper_status, this is the rule to start with:

paper_status Allowed

paper_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "paper_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every paper_status call is checked against it from then on.

FAQ

Questions about paper_status

What does the paper_status tool do? +

Report the scholarly store status: the catalog is served live via OpenAlex (~250M works), plus the local D1 indexed-corpus counts (papers with full text indexed, total indexed passages, per-source breakdown, last refresh timestamp). It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on paper_status? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for paper_status: 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 Livedatalink. Nothing to install.

What risk level is paper_status? +

paper_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit paper_status? +

Yes. Add a rate_limit block to the paper_status 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.

How do I block paper_status completely? +

Set action: deny in the PolicyLayer policy for paper_status. 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.

What MCP server provides paper_status? +

paper_status is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 280 Livedatalink tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →