search_by_book
AI agents call search_by_book to retrieve information from Pinecone Economic Books without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches or queries data from an economic books database. Consistent with sibling search tools on the same server, it retrieves information without modifying, deleting, or executing operations. The blast radius of misuse is minimal—an AI agent could retrieve irrelevant or excessive data, but cannot alter the database or trigger external effects.
From the tool's definition Tool name 'search_by_book' indicates a search/query function; sibling tools are all read-only search utilities (semantic_search, search_by_author, search_by_subject, get_by_id, get_authors, get_index_stats); server purpose is 'semantic search through a…
Attacks that exploit this kind of access
search_by_book. It is categorised as a Read tool in the Pinecone Economic Books MCP Server, which means it retrieves data without modifying state.
Register the Pinecone Economic Books MCP server in PolicyLayer and add a rule for search_by_book: 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 Pinecone Economic Books. Nothing to install.
search_by_book 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_by_book 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_by_book. 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_by_book is provided by the Pinecone Economic Books MCP server (srulyrosenblat/econ_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 →