stop_migration

Stop an ongoing database migration.

SERVERVultr MCP SOURCErsp2k/mcp-vultr

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rsp2k-mcp-vultr/stop-migration.md

WHAT IT DOES

What stop_migration does on Vultr MCP

AI agents invoke stop_migration to trigger actions in Vultr MCP. 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.

RISK

Why stop_migration is rated High

This is an Execute tool rather than Write or Destructive because it triggers a real-time operation with significant side effects (interrupting a data migration), but does not irreversibly delete data or permanently destroy infrastructure.

From the tool's definition Tool named 'stop_migration' with description 'Stop an ongoing database migration.' This directly triggers an external operation (halting a running migration process) whose effects are immediate and depend on the target migration specified as an argument.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stop_migration safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stop_migration, this is the rule to start with:

stop_migration Rate-limited

stop_migration 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_migration": {
      "limits": [
        {
          "counter": "stop_migration_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every stop_migration call is checked against it from then on.

FAQ

Questions about stop_migration

What does the stop_migration tool do? +

Stop an ongoing database migration. It is categorised as a Execute tool in the Vultr MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_migration? +

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

What risk level is stop_migration? +

stop_migration is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stop_migration? +

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

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

stop_migration is provided by the Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vultr, and thousands of servers like it.

This server

All 284 Vultr tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →