Hybrid search: vector search + expanded subgraphs.
AI agents call graph_search to retrieve information from MCP Roo Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs search queries against a graph-based memory store using vector search and subgraph traversal. It retrieves and returns data but does not create, modify, delete, execute external code, or move financial assets.
From the tool's definition Tool name 'graph_search' and description 'Hybrid search: vector search + expanded subgraphs' indicate retrieval and querying of existing graph data without modification, creation, or deletion. The verb 'search' is a classic Read operation.
Attacks that exploit this kind of access
Hybrid search: vector search + expanded subgraphs. It is categorised as a Read tool in the MCP Roo Memory MCP Server, which means it retrieves data without modifying state.
Register the MCP Roo Memory MCP server in PolicyLayer and add a rule for graph_search: 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 MCP Roo Memory. Nothing to install.
graph_search 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 graph_search 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 graph_search. 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.
graph_search is provided by the MCP Roo Memory MCP server (mcasdfgf/mcp-roo-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
graph_search is one line of MCP Roo Memory's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →