AI agents call get_memory to retrieve information from MemGPT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing conversation history without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal security impact—disclosure of conversation history may have privacy concerns but does not enable destructive or dangerous actions.
From the tool's definition Tool name 'get_memory' and description 'Retrieve conversation history' indicate a read-only retrieval operation with no data modification.
Documented attack patterns abuse exactly the kind of access get_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MemGPT MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_memory:
{
"version": "1",
"default": "deny",
"tools": {
"get_memory": {}
}
}get_memory 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.
Retrieve conversation history. It is categorised as a Read tool in the MemGPT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MemGPT MCP Server MCP server in PolicyLayer and add a rule for get_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 MemGPT MCP Server. Nothing to install.
get_memory 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 get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_memory is provided by the MemGPT MCP Server MCP server (vic563/memgpt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MemGPT MCP Server, 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.
5 MemGPT MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.