verify_migration
Reconcile a completed migration and persist its verification report after explicit user authorization. Requires confirm=true, workspace_id and migration_id. Uses durable transfer evidence and optional destination count readback according to the existing migration configuration; does not write des...
This record as markdown: /tools/sankahq-sanka-mcp/verify-migration.md
What verify_migration does on Sanka MCP Server
AI agents call verify_migration to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why verify_migration is rated Low
Even though verify_migration only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs verify_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 verify_migration, this is the rule to start with:
verify_migration is read-only, so it stays allowed. 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 verify_migration call is checked against it from then on.
Questions about verify_migration
Reconcile a completed migration and persist its verification report after explicit user authorization. Requires confirm=true, workspace_id and migration_id. Uses durable transfer evidence and optional destination count readback according to the existing migration configuration; does not write destination records or roll them back. Inspect returned ok, status, per-route results and individual checks: not_run does not mean passed. The current API does not perform field sampling. No plan_hash or body is accepted by this endpoint. An optional stable idempotency_key is supported; reuse it for identical retries. Automatic POST retries are disabled. If the response is uncertain, inspect get_migration_verification and get_migration before resubmitting. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for verify_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.
verify_migration is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the verify_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 verify_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.
verify_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