search_reflections
AI agents call search_reflections to retrieve information from Session Buddy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to search and retrieve stored reflections or learnings from session memory without modifying data. Semantic search operations are fundamentally retrieval-based with no side effects, making this a Read operation with low severity risk if misused by an AI agent.
From the tool's definition Tool name 'search_reflections' combined with server description's mention of 'semantic search for capturing learnings across coding sessions' indicates data retrieval capability.
Attacks that exploit this kind of access
search_reflections. It is categorised as a Read tool in the Session Buddy MCP Server, which means it retrieves data without modifying state.
Register the Session Buddy MCP server in PolicyLayer and add a rule for search_reflections: 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 Session Buddy. Nothing to install.
search_reflections 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_reflections 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_reflections. 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_reflections is provided by the Session Buddy MCP server (lesleslie/session-buddy). 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 →