Low Risk

query_memory

query_memory

How to control query_memory ↓

AI agents call query_memory to retrieve information from Forgetful without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The tool name and naming pattern within the server strongly suggest this is a data retrieval operation without side effects. The description is empty, reducing confidence slightly, but the contextual evidence from related tools (create_memory and delete_memory on same server) and the query_ prefix consistently indicates a Read operation that searches or retrieves memory data from the knowledge base.

From the tool's definition Tool name 'query_memory' indicates a retrieval operation. Server context describes 'semantic search and automatic linking' capabilities consistent with Read operations.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Forgetful, and nothing reaches the server without passing your rules. This is the rule we recommend for query_memory:

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

query_memory 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 Forgetful — 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.

Go deeper

What does the query_memory tool do? +

query_memory. It is categorised as a Read tool in the Forgetful MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_memory? +

Register the Forgetful MCP server in PolicyLayer and add a rule for query_memory: 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 Forgetful. Nothing to install.

What risk level is query_memory? +

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

Can I rate-limit query_memory? +

Yes. Add a rate_limit block to the query_memory 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 query_memory completely? +

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

query_memory is provided by the Forgetful MCP server (scottrbk/forgetful). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Forgetful tool call.

Deterministic rules across all 59 Forgetful tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

59 Forgetful tools catalogued and risk-classified — across an index of 42,500+ 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.