memory_migrate · Claude Crowed MCP: Risk & Policy

WHAT IT DOES

What memory_migrate does on Claude Crowed

AI agents invoke memory_migrate to trigger actions in Claude Crowed. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why memory_migrate needs a policy

Migration operations typically restructure, transform, or move data between schemas/stores. Given the server is a versioned document store, 'memory_migrate' likely executes a schema or data migration, which could modify data in place. With sibling tools spanning read/write/delete operations, migration fits Execute (or possibly Write/Destructive) best. However, with no description, confidence is low.

From the tool's definition Tool name 'memory_migrate' — description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_migrate Rate-limited

memory_migrate stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_migrate": {
      "limits": [
        {
          "counter": "memory_migrate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 Crowed, so you can run agents against it safely.

FAQ

Questions about memory_migrate

What does the memory_migrate tool do? +

memory_migrate. It is categorised as a Execute tool in the Claude Crowed MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on memory_migrate? +

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

What risk level is memory_migrate? +

memory_migrate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit memory_migrate? +

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

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

memory_migrate is provided by the Claude Crowed MCP server (thenewjavaman/claude-crowed). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.