List recently added/updated PhilArchive records in a date window, via OAI-PMH
AI agents call list_recent 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.
The tool retrieves metadata about recently updated philosophy papers without altering data, executing code, or triggering external side effects. It is a read-only query interface to a public archive's metadata feed. The OAI-PMH protocol is a standard metadata harvesting interface designed for non-destructive retrieval.
From the tool's definition Tool performs 'list' operation via OAI-PMH to retrieve recently added/updated records from PhilArchive metadata. Description indicates querying/browsing capability without modification or execution.
Attacks that exploit this kind of access
List recently added/updated PhilArchive records in a date window, 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 list_recent: 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.
list_recent 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 list_recent 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 list_recent. 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.
list_recent 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 →