start-migration · Awslabs Valkey MCP: Risk & Policy

WHAT IT DOES

What start-migration does on Awslabs Valkey

AI agents invoke start-migration to trigger actions in Awslabs Valkey. 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 are Execute-class because they trigger external operations and infrastructure changes whose effects depend on arguments. While potentially damaging, they are typically designed to be part of normal operational workflows rather than destructive deletions, hence Execute rather than Destructive. The high severity reflects the blast radius of a misconfigured or inadvertently triggered migration.

From the tool's definition Tool name 'start-migration' indicates initiation of a migration operation in ElastiCache/MemoryDB context.

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 Awslabs Valkey, 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 Awslabs Valkey 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 Awslabs Valkey 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 Awslabs Valkey. 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 Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.