Get list of references of this paper.
AI agents call get_paper_references to retrieve information from Scholar Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves bibliographic reference metadata from an academic paper—a pure read operation with no side effects, no code execution, no data modification, and no irreversible actions. The blast radius of misuse is minimal: an agent could only retrieve reference information already publicly available in academic databases.
From the tool's definition Tool name 'get_paper_references' and description 'Get list of references of this paper' indicate retrieval of existing data without modification, creation, or deletion.
Attacks that exploit this kind of access
Get list of references of this paper. It is categorised as a Read tool in the Scholar Search MCP Server, which means it retrieves data without modifying state.
Register the Scholar Search MCP server in PolicyLayer and add a rule for get_paper_references: 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 Search. Nothing to install.
get_paper_references 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 get_paper_references 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 get_paper_references. 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.
get_paper_references is provided by the Scholar Search MCP server (silung/scholar-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →