Fetch canonical metadata for one PhilArchive/PhilPapers record via OAI-PMH.
AI agents call get_paper to retrieve information from Philosophy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation to retrieve structured metadata about academic papers. It has no side effects, does not modify data, does not execute code, and does not involve financial transactions. The blast radius of misuse is minimal—an agent could retrieve metadata for many papers or request invalid IDs, but cannot alter data or cause harm beyond potential resource consumption.
From the tool's definition Tool 'get_paper' fetches metadata via OAI-PMH (Open Archives Initiative Protocol for Metadata Harvesting). The description explicitly states it retrieves 'canonical metadata' from PhilArchive/PhilPapers records.
Attacks that exploit this kind of access
Fetch canonical metadata for one PhilArchive/PhilPapers record via OAI-PMH. It is categorised as a Read tool in the Philosophy MCP Server, which means it retrieves data without modifying state.
Register the Philosophy MCP server in PolicyLayer and add a rule for get_paper: 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 Philosophy. Nothing to install.
get_paper 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 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. 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 is provided by the Philosophy MCP server (sea9401/philosophy-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 →