Search across Recon Book documentation (chapters, concepts, FAQs). Returns top 10 matches. Source: book.getrecon.xyz
AI agents call search_book to retrieve information from Recon Fuzz Knowledge 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 tool that retrieves and returns informational data from documentation sources. It has no capability to modify data, execute code, delete resources, or impact financial systems. The blast radius of misuse is minimal — an agent could only retrieve available documentation content.
From the tool's definition Tool description states it 'Search across Recon Book documentation' and 'Returns top 10 matches' — a query operation with no side effects. No modification, deletion, execution, or financial impact is possible.
Attacks that exploit this kind of access
Search across Recon Book documentation (chapters, concepts, FAQs). Returns top 10 matches. Source: book.getrecon.xyz. It is categorised as a Read tool in the Recon Fuzz Knowledge MCP Server, which means it retrieves data without modifying state.
Register the Recon Fuzz Knowledge MCP server in PolicyLayer and add a rule for search_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 Recon Fuzz Knowledge. Nothing to install.
search_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_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_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_book is provided by the Recon Fuzz Knowledge MCP server (recon-fuzz/recon-mcp-knowledge). 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 →