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...
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.
Attacks that exploit this kind of access
The rule that runs repair_migration safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For repair_migration, this is the rule to start with:
repair_migration 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every repair_migration call is checked against it from then on.
Questions about 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 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.
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.
repair_migration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
This server
Across the catalogue