Search Project Gutenberg for public-domain classics and out-of-copyright translations
AI agents call search_gutenberg 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 search query against Project Gutenberg, a public digital library. Searching is a retrieval operation with no side effects—it cannot create, modify, delete, or execute anything. The worst-case misuse would be retrieving unwanted text results, which constitutes minimal harm. It belongs in the Read category with low severity.
From the tool's definition Tool name 'search_gutenberg' and description 'Search Project Gutenberg for public-domain classics' indicate a search operation that retrieves metadata or query results from a read-only repository.
Attacks that exploit this kind of access
Search Project Gutenberg for public-domain classics and out-of-copyright translations. 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_gutenberg: 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_gutenberg 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_gutenberg 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_gutenberg. 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_gutenberg 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 →