Search across Lenny Rachitsky podcast transcripts for insights,
AI agents call search_lenny to retrieve information from Lenny RAG MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs semantic search over podcast transcripts to retrieve information. It retrieves or queries data without creating, modifying, deleting, or executing anything. No side effects result from searching. This is a classic Read operation with minimal risk if misused by an AI agent—it can only surface existing podcast content, not alter it or trigger external effects.
From the tool's definition Tool name 'search_lenny' and description 'Search across Lenny Rachitsky podcast transcripts for insights' indicate a search/retrieval operation.
Documented attack patterns abuse exactly the kind of access search_lenny gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lenny RAG MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_lenny:
{
"version": "1",
"default": "deny",
"tools": {
"search_lenny": {}
}
}search_lenny is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search across Lenny Rachitsky podcast transcripts for insights,. It is categorised as a Read tool in the Lenny RAG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lenny RAG MCP Server MCP server in PolicyLayer and add a rule for search_lenny: 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 Lenny RAG MCP Server. Nothing to install.
search_lenny 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_lenny 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_lenny. 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_lenny is provided by the Lenny RAG MCP Server MCP server (mpnikhil/lenny-rag-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lenny RAG MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Lenny RAG MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.