memory_move · MCP Associative Memory Server MCP

WHAT IT DOES

What memory_move does on MCP Associative Memory Server

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

WHY IT NEEDS A POLICY

Why memory_move needs a policy

This tool modifies the state of memory records by relocating them within the system's hierarchy or scope structure. While not destructive (the data persists), it is a write-class operation that alters data organization and potentially accessibility. The severity is medium because scope changes could affect visibility/permissions but the operation remains reversible (memories can be moved back).

From the tool's definition Tool performs 'Move memories to a new scope' — a modification operation that changes the organizational location/scope of stored data without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_move Rate-limited

memory_move 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_move": {
      "limits": [
        {
          "counter": "memory_move_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 MCP Associative Memory Server, so you can run agents against it safely.

FAQ

Questions about memory_move

What does the memory_move tool do? +

Move memories to a new scope. It is categorised as a Write tool in the MCP Associative Memory 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 memory_move? +

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

What risk level is memory_move? +

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

Can I rate-limit memory_move? +

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

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

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