Search project memories with filters (query, type, tags, importance).
AI agents call search_memories to retrieve information from Code Graph Knowledge System without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that searches and filters existing data (project memories) with no side effects. No data is created, modified, deleted, or executed. The filters (query, type, tags, importance) are selection parameters, not actions. This falls squarely into the Read category with low severity since misuse would only expose information already stored in the system.
From the tool's definition Tool name is 'search_memories' and description states it 'Search[es] project memories with filters' — a query operation that retrieves data without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access search_memories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Code Graph Knowledge System, and nothing reaches the server without passing your rules. This is the rule we recommend for search_memories:
{
"version": "1",
"default": "deny",
"tools": {
"search_memories": {}
}
}search_memories 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 project memories with filters (query, type, tags, importance). It is categorised as a Read tool in the Code Graph Knowledge System MCP Server, which means it retrieves data without modifying state.
Register the Code Graph Knowledge System MCP server in PolicyLayer and add a rule for search_memories: 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 Code Graph Knowledge System. Nothing to install.
search_memories 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_memories 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_memories. 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_memories is provided by the Code Graph Knowledge System MCP server (royisme/codebase-rag). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Code Graph Knowledge System, 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.
30 Code Graph Knowledge System tools catalogued and risk-classified — across an index of 43,000+ MCP servers.