Modify the shard configuration of an existing Amazon ElastiCache replication group. This tool modifies the shard configuration of an existing replication group by: - Modifying the number of replicas in a shard - Specifying preferred availability zones for replicas Parameters: replication_gr...
Part of the AWS ElastiCache MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use modify-replication-group-shard-configuration 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 modify-replication-group-shard-configuration 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:
modify-replication-group-shard-configuration:
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 modify-replication-group-shard-configuration 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.
Modify the shard configuration of an existing Amazon ElastiCache replication group. This tool modifies the shard configuration of an existing replication group by: - Modifying the number of replicas in a shard - Specifying preferred availability zones for replicas Parameters: replication_group_id (str): The identifier of the replication group to modify. node_group_count (int): The number of node groups (shards) in the replication group. apply_immediately (Optional[bool]): Whether to apply changes immediately or during maintenance window. resharding_configuration (Optional[Union[str, List[Dict]]]): Resharding configuration in either shorthand string format or list of dictionaries format. Shorthand format: "NodeGroupId=string,NewShardConfiguration={NewReplicaCount=integer,PreferredAvailabilityZones=string1,string2}" Multiple configurations can be separated by spaces. JSON format: List of dictionaries with required fields: - NodeGroupId: string - NewShardConfiguration: - NewReplicaCount: integer - PreferredAvailabilityZones: list of strings (optional) Returns: Dict containing information about the modified replication group.. 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 modify-replication-group-shard-configuration. 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.
modify-replication-group-shard-configuration 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 modify-replication-group-shard-configuration 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 modify-replication-group-shard-configuration. 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.
modify-replication-group-shard-configuration 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.