Complete migration to an Amazon ElastiCache replication group. This tool completes the migration of data from a Redis instance to an ElastiCache replication group. It finalizes the data migration process and transitions the replication group to normal operation. Args: request: The CompleteM...
Part of the AWS ElastiCache MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use complete-migration to create or modify resources in AWS ElastiCache MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call complete-migration repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AWS ElastiCache MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
complete-migration:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full AWS ElastiCache MCP Server policy for all 39 tools.
Agents calling write-class tools like complete-migration have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Complete migration to an Amazon ElastiCache replication group. This tool completes the migration of data from a Redis instance to an ElastiCache replication group. It finalizes the data migration process and transitions the replication group to normal operation. Args: request: The CompleteMigrationRequest object containing: - replication_group_id: The ID of the replication group to which data is being migrated - force: (Optional) Forces the migration to stop without ensuring that data is in sync. It is recommended to use this option only to abort the migration and not recommended when application wants to continue migration to ElastiCache. Returns: Dict containing information about the migration completion result.. It is categorised as a Write tool in the AWS ElastiCache MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for complete-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.
complete-migration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the complete-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.
Set action: deny in the Intercept policy for complete-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.
complete-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.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.