New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

repair_migration

Retry failed records/relationships through the existing execution journal without changing the reviewed plan. Requires explicit authorization for destination writes and the server-metered repair charge (currently 300 Sanka Credits on completed repair), exact reviewed plan hash and stable idempote...

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sankahq-sanka-mcp/repair-migration.md

What repair_migration does on Sanka MCP Server

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

Why repair_migration is rated Medium

An AI agent can call repair_migration faster than any human can review: one bad instruction and it creates or modifies resources in Sanka MCP Server by the hundred, each call as confident as the last.

Questions about repair_migration

What does the repair_migration tool do? +

Retry failed records/relationships through the existing execution journal without changing the reviewed plan. Requires explicit authorization for destination writes and the server-metered repair charge (currently 300 Sanka Credits on completed repair), exact reviewed plan hash and stable idempotency key. Failed verification must identify repairable records. This is not a structural mapping edit or automatic recovery. It is categorised as a Write tool in the Sanka MCP 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 repair_migration? +

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

What risk level is repair_migration? +

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

Can I rate-limit repair_migration? +

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

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

repair_migration is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Sanka MCP Server, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sanka MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.