Search the Recon glossary for terms matching a query. Returns top 5 matching glossary terms with full definitions. Source: getrecon.xyz
AI agents call search_glossary 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 tool retrieves glossary definitions in response to a search query. It has no side effects, does not modify data, and does not execute code or trigger external operations. It is purely informational retrieval, fitting the 'Read' category. Low severity because misuse (e.g., searching for many terms) would only result in reading existing definitions with minimal blast radius.
From the tool's definition Tool description states it 'search[es] the Recon glossary for terms matching a query' and 'returns top 5 matching glossary terms with full definitions.' The verb 'search' and the retrieval-only nature (returns data with no modification) indicate a read-only…
Attacks that exploit this kind of access
Search the Recon glossary for terms matching a query. Returns top 5 matching glossary terms with full definitions. Source: 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_glossary: 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_glossary 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_glossary 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_glossary. 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_glossary 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 →