search_all

Search across ALL Recon content — getrecon.xyz (blog, glossary, comparisons, tools), book.getrecon.xyz (chapters, concepts, FAQs), and getrecon.substack.com (newsletter posts). Returns top 15 matches with source labels.

Server Recon Fuzz Knowledge recon-fuzz/recon-mcp-knowledge
Category Read
Risk class Low
Parameters 00 required

What search_all does on Recon Fuzz Knowledge

AI agents call search_all 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.

Why search_all needs a policy

This tool retrieves and queries data across multiple knowledge sources (blog, book, newsletter) without any side effects, modifications, or execution capabilities. It is a straightforward search/retrieval operation that matches the Read category definition.

From the tool's definition Tool name 'search_all' and description states it 'Search[es] across ALL Recon content' and 'Returns top 15 matches with source labels.' No modification, deletion, execution, or financial operations are described.

Risk signalsBulk/mass operation — affects multiple targets

Questions about search_all

What does the search_all tool do? +

Search across ALL Recon content — getrecon.xyz (blog, glossary, comparisons, tools), book.getrecon.xyz (chapters, concepts, FAQs), and getrecon.substack.com (newsletter posts). Returns top 15 matches with source labels. It is categorised as a Read tool in the Recon Fuzz Knowledge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_all? +

Register the Recon Fuzz Knowledge MCP server in PolicyLayer and add a rule for search_all: 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.

What risk level is search_all? +

search_all is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_all? +

Yes. Add a rate_limit block to the search_all 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.

How do I block search_all completely? +

Set action: deny in the PolicyLayer policy for search_all. 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.

What MCP server provides search_all? +

search_all 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.