memory_make_portable · Claude Memory MCP: Risk & Policy

WHAT IT DOES

What memory_make_portable does on Claude Memory MCP

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

WHY IT NEEDS A POLICY

Why memory_make_portable needs a policy

This tool creates or modifies the storage organization of project data by relocating the database file into the project directory (for git sharing). This is a reversible structural change to where data is stored, not a query (Read), not code execution (Execute), and not irreversible deletion (Destructive). It qualifies as Write.

From the tool's definition Tool moves/transfers the project database into the project directory, which modifies the storage structure and state of the project's persistent memory system. The verb 'Move' indicates a write-class operation that relocates and potentially restructures data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_make_portable Rate-limited

memory_make_portable 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_make_portable": {
      "limits": [
        {
          "counter": "memory_make_portable_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 Claude Memory MCP, so you can run agents against it safely.

FAQ

Questions about memory_make_portable

What does the memory_make_portable tool do? +

Move the project's DB into the project directory for git sharing. It is categorised as a Write tool in the Claude Memory MCP 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_make_portable? +

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

What risk level is memory_make_portable? +

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

Can I rate-limit memory_make_portable? +

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

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

memory_make_portable is provided by the Claude Memory MCP server (navid-kianfar/claude-memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.