Search across all Recon Substack posts. Returns top 10 matches with titles, dates, and content snippets.
AI agents call search_substack 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 queries existing Substack post data, returning search results. It has no side effects, does not modify data, execute code, delete information, or involve financial transactions. It is a straightforward read operation with minimal blast radius if misused by an AI agent—the worst outcome would be retrieval of unintended public posts.
From the tool's definition Tool description states it 'Search[es] across all Recon Substack posts' and 'Returns top 10 matches with titles, dates, and content snippets.' This is a query/search operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search across all Recon Substack posts. Returns top 10 matches with titles, dates, and content snippets. 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_substack: 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_substack 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_substack 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_substack. 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_substack 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 →