migrate_to_project · Engram MCP: Risk & Policy

WHAT IT DOES

What migrate_to_project does on Engram

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

WHY IT NEEDS A POLICY

Why migrate_to_project needs a policy

This tool creates or modifies data by reassigning memories between projects. While it doesn't delete data, it irreversibly changes where memories are stored/grouped within the system. It's Write rather than Destructive because the data itself persists—only its organizational location changes.

From the tool's definition Tool description states 'Mueve memorias' (moves memories) from a source project to a destination project based on a tag. This is a data migration operation that modifies the project assignment of memories.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

migrate_to_project Rate-limited

migrate_to_project 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": {
    "migrate_to_project": {
      "limits": [
        {
          "counter": "migrate_to_project_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 Engram, so you can run agents against it safely.

FAQ

Questions about migrate_to_project

What does the migrate_to_project tool do? +

Mueve memorias que contengan un tag específico desde un proyecto origen a un proyecto destino. It is categorised as a Write tool in the Engram MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on migrate_to_project? +

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

What risk level is migrate_to_project? +

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

Can I rate-limit migrate_to_project? +

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

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

migrate_to_project is provided by the Engram MCP server (jacksini/engram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.