get_paper_metadata
AI agents call get_paper_metadata to retrieve information from Academic MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves bibliographic and metadata information from academic databases. It queries existing data without creating, modifying, deleting, or executing operations. The blast radius of misuse is minimal—an AI agent could retrieve excessive metadata or spam requests, but cannot alter databases or cause financial harm.
From the tool's definition Tool name 'get_paper_metadata' and server context indicate data retrieval. Server description emphasizes 'search across multiple academic databases' and 'metadata retrieval' with no mention of modification or deletion capabilities.
Attacks that exploit this kind of access
get_paper_metadata. It is categorised as a Read tool in the Academic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Academic MCP Server MCP server in PolicyLayer and add a rule for get_paper_metadata: 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 Academic MCP Server. Nothing to install.
get_paper_metadata 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_metadata 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_metadata. 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_metadata is provided by the Academic MCP Server MCP server (nanyang12138/academic-mcp-server). 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 →