start-migration · Amazon MQ MCP Server MCP: Risk & Policy

WHAT IT DOES

What start-migration does on Amazon MQ MCP Server

AI agents invoke start-migration to trigger actions in Amazon MQ MCP Server. 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.

WHY IT NEEDS A POLICY

Why start-migration needs a policy

Migration operations trigger external processes that reconfigure or move data across systems. While not immediately destructive (reversible in some cases), they execute complex operations with significant blast radius if misconfigured by an AI agent (downtime, data inconsistency, service interruption). Without explicit documentation, conservatively classify as Execute rather than Write.

From the tool's definition Tool named 'start-migration' on Amazon MQ server with description empty. Based on context (AMQ broker management), migration operations typically involve executing infrastructure changes, data movement, and system reconfigurations across broker instances.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start-migration Rate-limited

start-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": {
    "start-migration": {
      "limits": [
        {
          "counter": "start-migration_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Amazon MQ MCP Server, so you can run agents against it safely.

FAQ

Questions about start-migration

What does the start-migration tool do? +

start-migration. It is categorised as a Execute tool in the Amazon MQ MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start-migration? +

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

What risk level is start-migration? +

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

Can I rate-limit start-migration? +

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

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

start-migration is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.