search_conversation_memory
AI agents call search_conversation_memory to retrieve information from Cluster Execution MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name suggests searching/querying existing conversation memory data without modification. Despite the empty description lowering confidence, the verb 'search' and lack of any mutative indicators (create, delete, update, execute) point to Read category. The low severity reflects that retrieving conversation data typically has minimal blast radius compared to destructive or financial operations.
From the tool's definition Tool name 'search_conversation_memory' indicates a query or retrieval operation on stored conversation data. No description provided to confirm mutative operations.
Attacks that exploit this kind of access
search_conversation_memory. It is categorised as a Read tool in the Cluster Execution MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cluster Execution MCP Server MCP server in PolicyLayer and add a rule for search_conversation_memory: 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 Cluster Execution MCP Server. Nothing to install.
search_conversation_memory 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_conversation_memory 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_conversation_memory. 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_conversation_memory is provided by the Cluster Execution MCP Server MCP server (marc-shade/cluster-execution-mcp). 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 →