AI agents invoke migrate_data to trigger actions in Project Tessera. 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.
Data migrations typically execute a process that restructures, transforms, or moves data between schemas or storage locations. This can have destructive side effects (overwriting or dropping old structures) but the description is minimal and uninformative, so the exact behavior is unclear. 'Run' implies execution of an operation with side effects.
From the tool's definition 'Run data migration' — the verb 'run' and the concept of 'migration' indicate execution of a process that transforms or moves data, potentially irreversibly.
Documented attack patterns abuse exactly the kind of access migrate_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Project Tessera, and nothing reaches the server without passing your rules. This is the rule we recommend for migrate_data:
{
"version": "1",
"default": "deny",
"tools": {
"migrate_data": {
"limits": [
{
"counter": "migrate_data_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}migrate_data 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.
Free to start. No card required.
Run data migration. It is categorised as a Execute tool in the Project Tessera MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Project Tessera MCP server in PolicyLayer and add a rule for migrate_data: 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 Project Tessera. Nothing to install.
migrate_data is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the migrate_data 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.
Set action: deny in the PolicyLayer policy for migrate_data. 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.
migrate_data is provided by the Project Tessera MCP server (besslframework-stack/project-tessera). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Project Tessera, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
43 Project Tessera tools catalogued and risk-classified — across an index of 43,000+ MCP servers.