get-memories

THE RISK

Low Risk

Why get-memories needs a policy

This tool queries and returns stored memory data without modifying, deleting, or executing any operations. It is a straightforward data retrieval function that reads from MongoDB persistence. The blast radius of misuse is minimal—an agent could retrieve unwanted memories but cannot alter or destroy data.

From the tool's definition Tool name 'get-memories' and description 'Retrieve all memories from the database' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get-memories gives an agent:

POLICY

How to control get-memories

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-memories": {}
  }
}

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

Create a free account and register Memory MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Memory MCP tools

Destructive clear-memories Clear all memories from the database Write add-memories Add new memories to the database without overwriting existing ones Write archive-context Archive context messages for a conversation with tags and metadata Write create-summary Create a summary of context items and link them to the summary Write save-memories Save all memories to the database, overwriting existing ones Read get-conversation-summaries Get all summaries for a specific conversation Read retrieve-context Retrieve relevant archived context for a conversation Read search-context-by-tags Search archived context and summaries by tags

All 10 Memory MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get-memories

What does the get-memories tool do? +

Retrieve all memories from the database. It is categorised as a Read tool in the Memory MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-memories? +

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

What risk level is get-memories? +

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

Can I rate-limit get-memories? +

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

How do I block get-memories completely? +

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

What MCP server provides get-memories? +

get-memories is provided by the Memory MCP server (jamesanz/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Memory MCP tool call.

Start from Memory MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →