Search the Directory of Open Access Books — peer-reviewed, fully open-access academic
AI agents call search_doab 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 retrieves and queries data from an open-access academic book directory without side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' Severity is low because the worst outcome of misuse is irrelevant search results or information disclosure from public open-access sources, with no impact on data integrity, system availability, or…
From the tool's definition Tool name 'search_doab' and description indicate searching/querying the Directory of Open Access Books. No modification, deletion, or execution capability is described. Returns query results from a public academic database.
Attacks that exploit this kind of access
Search the Directory of Open Access Books — peer-reviewed, fully open-access academic. 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_doab: 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_doab 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_doab 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_doab. 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_doab 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 →