memory_update_long_term

Server Universal Memory slicenferqin/universal-memory-mcp

Category Write

Risk class Medium

Parameters 00 required

WHAT IT DOES

What memory_update_long_term does on Universal Memory

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

WHY IT NEEDS A POLICY

Why memory_update_long_term needs a policy

An AI agent can call memory_update_long_term faster than any human can review — one bad instruction and it creates or modifies resources in Universal Memory by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_update_long_term Rate-limited

memory_update_long_term 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": {
    "memory_update_long_term": {
      "limits": [
        {
          "counter": "memory_update_long_term_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 Universal Memory, so you can run agents against it safely.

FAQ

Questions about memory_update_long_term

What does the memory_update_long_term tool do? +

Store important information in long-term memory for easy retrieval. WHEN TO USE - Call this when you identify: - User preferences (coding style, tools, communication preferences) - Important decisions (architecture choices, technology selections) - Key facts about user or their projects - Contact information or team details Categories: - preferences: User. It is categorised as a Write tool in the Universal Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_update_long_term? +

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

What risk level is memory_update_long_term? +

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

Can I rate-limit memory_update_long_term? +

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

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

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