Keyword search across PhilPapers / PhilArchive (philosophy preprints and published
AI agents call search_papers 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 is a search/query operation that retrieves information about philosophy papers without side effects. It does not create, modify, delete, or execute anything. The tool fits the 'Read' category as it queries and retrieves data from academic archives. Severity is low because misuse would only result in retrieving irrelevant or excessive search results, with no harmful blast radius.
From the tool's definition Tool name 'search_papers' and description indicate keyword search functionality across philosophy paper archives (PhilPapers/PhilArchive). No mention of modification, deletion, or execution capabilities. Returns search results only.
Attacks that exploit this kind of access
Keyword search across PhilPapers / PhilArchive (philosophy preprints and published. 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 search_papers: 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.
search_papers 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 search_papers 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 search_papers. 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.
search_papers 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 →