get_memories

List memories chronologically. Use when you need to browse all stored memories rather than search by relevance. Prefer search_memories for finding specific information.

Server Memsolus MCP Server memsolus/mcp
Category Read
Risk class Low
Parameters 00 required

What get_memories does on Memsolus MCP Server

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

Why get_memories needs a policy

This tool retrieves and lists existing memory data without creating, modifying, deleting, or executing any operations. It has no side effects beyond data retrieval. The primary risk is information disclosure if the agent accesses sensitive stored memories, but that is typical for read operations and carries low severity in isolation.

From the tool's definition Tool description states: 'List memories chronologically' and 'when you need to browse all stored memories' - these are retrieval operations with no modification capability.

Questions about get_memories

What does the get_memories tool do? +

List memories chronologically. Use when you need to browse all stored memories rather than search by relevance. Prefer search_memories for finding specific information. It is categorised as a Read tool in the Memsolus MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_memories? +

Register the Memsolus MCP Server 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 Memsolus MCP Server. 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 Memsolus MCP Server MCP server (memsolus/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.