Low Risk

test-migration

Test migration to an Amazon ElastiCache replication group. This tool tests migration from a Redis instance to an ElastiCache replication group. It validates that data can be successfully migrated from the specified endpoint to the target replication group. Args: request: The TestMigrationRe...

Part of the AWS ElastiCache MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call test-migration to retrieve information from AWS ElastiCache MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though test-migration only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

aws-elasticache-mcp-server.yaml
tools:
  test-migration:
    rules:
      - action: allow

See the full AWS ElastiCache MCP Server policy for all 39 tools.

Tool Name test-migration
Category Read
Risk Level Low

View all 39 tools →

Agents calling read-class tools like test-migration have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the test-migration tool do? +

Test migration to an Amazon ElastiCache replication group. This tool tests migration from a Redis instance to an ElastiCache replication group. It validates that data can be successfully migrated from the specified endpoint to the target replication group. Args: request: The TestMigrationRequest object containing: - replication_group_id: The ID of the replication group to which data is to be migrated - customer_node_endpoint_list: List of endpoints from which data should be migrated. List should have only one element with Address and Port fields. Returns: Dict containing information about the migration test result.. It is categorised as a Read tool in the AWS ElastiCache MCP Server MCP Server, which means it retrieves data without modifying state.

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

Add a rule in your Intercept YAML policy under the tools section for test-migration. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS ElastiCache MCP Server MCP server.

What risk level is test-migration? +

test-migration is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit test-migration? +

Yes. Add a rate_limit block to the test-migration rule in your Intercept 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 test-migration completely? +

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

test-migration is provided by the AWS ElastiCache MCP Server MCP server (awslabs.elasticache-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.