// SCAN REPORT

Memsolus MCP Server

17 tools. 5 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 3 Jul 2026

5 can modify or destroy data

12 read-only

17 tools total

Community server · catalogue entry verified 03/07/2026

How to control Memsolus MCP Server ↓

TOOL MAP

What Memsolus MCP Server exposes to your agents

Read (12) Write / Execute (4) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Memsolus MCP Server tools

Destructive · High delete_memory This tool irreversibly removes stored data (memories) from the agent's persistent knowledge store. Write · Medium add_memory add_memory creates and stores new data in a persistent knowledge graph/memory system. Write · Medium promote_memory This tool modifies stored data by changing a memory's classification from temporary to permanent storage. Write · Low submit_feedback This tool creates or modifies feedback metadata reversibly—feedback can be changed, corrected, or removed without destroying underlying data.

5 of Memsolus MCP Server's 17 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Memsolus MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Memsolus MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_memory": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_memory": {
    "limits": [
      {
        "counter": "add_memory_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_dashboard_summary": {
    "limits": [
      {
        "counter": "get_dashboard_summary_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Memsolus MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MEMSOLUS →

Instant setup, no code required.

FULL CATALOGUE

All 17 Memsolus MCP Server tools

DESTRUCTIVE 1 tools

Destructive delete_memory Permanently delete a memory. Use when the user explicitly asks to forget something, or when a memory is clearl

WRITE 4 tools

Write add_memory Store a new persistent memory. Use when the user shares a fact, preference, decision, or any context worth rem Write promote_memory Promote a TASK-layer memory (temporary, with expiration) to RAW-layer (permanent, no expiration). Use when a m Write submit_feedback Submit quality feedback on a memory. Use POSITIVE when a memory proved accurate and useful. Use NEGATIVE when Write update_memory Update an existing memory

READ 12 tools

Read get_dashboard_summary Get workspace KPIs — total memories, searches, tokens used — with comparison to the previous period. Use when Read get_knowledge Get the consolidated knowledge profile built from processed memories. Use at the start of conversations to loa Read get_knowledge_entry Retrieve a specific knowledge entry by ID. Use when you need the full details of a particular knowledge entry, Read get_memories List memories chronologically. Use when you need to browse all stored memories rather than search by relevance Read get_memory Retrieve a specific memory by ID. Use when you already know the memory ID from a previous search or list resul Read get_memory_history Get the event history of a memory — creation, updates, promotions, and feedback. Use when you need to understa Read get_memory_profile Get a summarized profile of a user built from their memories — key topics, entity count, and a narrative summa Read graph_query Answer a natural language question using the knowledge graph. Use for complex relational questions like Read graph_search Search for entities in the knowledge graph. Use when you need to find people, organizations, places, or things Read graph_traverse Traverse relationships from a known entity in the knowledge graph. Use when you want to explore what an entity Read list_entities List all users and agents in the workspace with their memory counts. Use when you need to discover who has mem Read search_memories Search across stored memories using semantic, keyword, or hybrid search. Use when you need past context about

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Memsolus MCP Server

Can an AI agent delete data through the Memsolus MCP Server MCP server? +

Yes. The Memsolus MCP Server server exposes 1 destructive tools including delete_memory. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Memsolus MCP Server? +

The Memsolus MCP Server server has 4 write tools including add_memory, promote_memory, submit_feedback. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Memsolus MCP Server.

How many tools does the Memsolus MCP Server MCP server expose? +

17 tools across 3 categories: Destructive, Read, Write. 12 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on Memsolus MCP Server? +

Register the Memsolus MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Memsolus MCP Server tool call.

Deterministic rules across all 17 Memsolus MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MEMSOLUS →

Instant setup, no code required.

17 Memsolus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.