AI agents call search_summaries to retrieve information from Brain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'search_summaries' and its position among other read-only cognitive tools (tunnel_state, thinking_trajectory, bob_search) suggests it retrieves or queries summarized conversation data without modifying, deleting, or executing external operations. Despite the empty description lowering confidence, the naming convention and server design indicate read-only behavior.
From the tool's definition Tool named 'search_summaries' with empty description, but inferred from server context as a search/query tool for indexed conversation summaries. Sibling tools like 'bob_search' and 'bob_recent' indicate read-only access patterns.
Documented attack patterns abuse exactly the kind of access search_summaries gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Brain, and nothing reaches the server without passing your rules. This is the rule we recommend for search_summaries:
{
"version": "1",
"default": "deny",
"tools": {
"search_summaries": {}
}
}search_summaries 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_summaries. It is categorised as a Read tool in the Brain MCP Server, which means it retrieves data without modifying state.
Register the Brain MCP server in PolicyLayer and add a rule for search_summaries: 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 Brain. Nothing to install.
search_summaries 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_summaries 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_summaries. 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_summaries is provided by the Brain MCP server (mordechaipotash/brain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Brain, 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.
34 Brain tools catalogued and risk-classified — across an index of 43,000+ MCP servers.