Low Risk

suggest_memory_from_query

suggest_memory_from_query

How to control suggest_memory_from_query ↓

What suggest_memory_from_query does on Code Graph Knowledge System

AI agents call suggest_memory_from_query 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.

Low Risk

Why suggest_memory_from_query needs a policy

The tool name strongly suggests it retrieves or generates suggestions from existing query data (Read category). The empty description prevents higher confidence, but contextual analysis of the name and comparison to sibling tools (which include write operations like 'add_*' and destructive operations like 'clear_knowledge_base') indicates this tool performs a non-mutating query operation.

From the tool's definition Tool name 'suggest_memory_from_query' indicates a query-based suggestion/retrieval operation. The prefix 'suggest_' and suffix '_from_query' imply data retrieval or inference without modification.

Documented attack patterns abuse exactly the kind of access suggest_memory_from_query gives an agent:

How to control suggest_memory_from_query

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 suggest_memory_from_query:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "suggest_memory_from_query": {}
  }
}

suggest_memory_from_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Code Graph Knowledge System — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about suggest_memory_from_query

What does the suggest_memory_from_query tool do? +

suggest_memory_from_query. It is categorised as a Read tool in the Code Graph Knowledge System MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on suggest_memory_from_query? +

Register the Code Graph Knowledge System MCP server in PolicyLayer and add a rule for suggest_memory_from_query: 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.

What risk level is suggest_memory_from_query? +

suggest_memory_from_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit suggest_memory_from_query? +

Yes. Add a rate_limit block to the suggest_memory_from_query 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.

How do I block suggest_memory_from_query completely? +

Set action: deny in the PolicyLayer policy for suggest_memory_from_query. 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.

What MCP server provides suggest_memory_from_query? +

suggest_memory_from_query 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.

Enforce policy on every Code Graph Knowledge System tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.