List all developer tools documented on getrecon.xyz. Returns up to 20 tools with descriptions and URLs.
AI agents call list_tools 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 and displays a list of publicly documented developer tools with metadata (descriptions and URLs). It performs no data modification, deletion, code execution, or financial operations. The action is read-only information retrieval with no blast radius if called by an AI agent.
From the tool's definition Tool name 'list_tools' and description 'List all developer tools documented on getrecon.xyz. Returns up to 20 tools with descriptions and URLs.' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List all developer tools documented on getrecon.xyz. Returns up to 20 tools with descriptions and URLs. 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 list_tools: 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.
list_tools 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 list_tools 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 list_tools. 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.
list_tools 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 →