update_long_term_memory · Memory MCP Server MCP

WHAT IT DOES

What update_long_term_memory does on Memory MCP Server

AI agents use update_long_term_memory to create or update resources in Memory MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memory MCP Server environment.

WHY IT NEEDS A POLICY

Why update_long_term_memory needs a policy

The tool modifies stored memory entries in a controlled, reversible manner (updating fields like trigger conditions or content). This fits the Write category—it creates or modifies data reversibly.

From the tool's definition Tool name includes 'update' and description states 'Update an existing long-term memory' with capability to modify 'trigger condition, prompt content, or add update context.' This is reversible modification of data without deletion or execution of external…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_long_term_memory Rate-limited

update_long_term_memory stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_long_term_memory": {
      "limits": [
        {
          "counter": "update_long_term_memory_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Memory MCP Server, so you can run agents against it safely.

FAQ

Questions about update_long_term_memory

What does the update_long_term_memory tool do? +

Update an existing long-term memory. You can update the trigger condition, prompt content, or add update context. It is categorised as a Write tool in the Memory MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_long_term_memory? +

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

What risk level is update_long_term_memory? +

update_long_term_memory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_long_term_memory? +

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

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

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