Medium Risk

create-serverless-cache

Create a new Amazon ElastiCache serverless cache. This tool creates a new serverless cache with specified configuration including: - Serverless cache name and capacity - Optional VPC and security settings - Optional encryption settings - Optional snapshot restoration and backup settings - Option...

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

AI agents use create-serverless-cache 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 create-serverless-cache 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.

aws-elasticache-mcp-server.yaml
tools:
  create-serverless-cache:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

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

Tool Name create-serverless-cache
Category Write
Risk Level Medium

View all 39 tools →

Agents calling write-class tools like create-serverless-cache 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 Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the create-serverless-cache tool do? +

Create a new Amazon ElastiCache serverless cache. This tool creates a new serverless cache with specified configuration including: - Serverless cache name and capacity - Optional VPC and security settings - Optional encryption settings - Optional snapshot restoration and backup settings - Optional usage limits and user groups - Optional tags Parameters: serverless_cache_name (str): Name of the serverless cache. engine (str): Cache engine type. description (Optional[str]): Description for the cache. kms_key_id (Optional[str]): KMS key ID for encryption. major_engine_version (Optional[str]): Major engine version. snapshot_arns_to_restore (Optional[List[str]]): List of snapshot ARNs to restore from. subnet_ids (Optional[List[str]]): List of subnet IDs for VPC configuration. tags (Optional[Union[str, List[Dict[str, Optional[str]]], Dict[str, Optional[str]]]]): Tags to apply to the cache. Tag requirements: - Key: (string) Required. The key for the tag. Must not be empty. - Value: (string) Optional. The tag's value. May be null. Supports three formats: 1. Shorthand syntax: "Key=value,Key2=value2" or "Key=,Key2=" for null values 2. Dictionary: {"key": "value", "key2": null} 3. JSON array: [{"Key": "string", "Value": "string"}, {"Key": "string2", "Value": null}] Can be None if no tags are needed. security_group_ids (Optional[List[str]]): List of security group IDs. cache_usage_limits (Optional[CacheUsageLimits]): Usage limits for the cache. Structure: { "DataStorage": { "Maximum": int, # Maximum storage in GB "Minimum": int, # Minimum storage in GB "Unit": "GB" # Storage unit (currently only GB is supported) }, "ECPUPerSecond": { "Maximum": int, # Maximum ECPU per second "Minimum": int # Minimum ECPU per second } } user_group_id (Optional[str]): ID of the user group to associate with the cache. snapshot_retention_limit (Optional[int]): Number of days for which ElastiCache retains automatic snapshots. daily_snapshot_time (Optional[str]): Time range (in UTC) when daily snapshots are taken (e.g., '04:00-05:00'). Returns: Dict containing information about the created serverless cache.. 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.

How do I enforce a policy on create-serverless-cache? +

Add a rule in your Intercept YAML policy under the tools section for create-serverless-cache. 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 create-serverless-cache? +

create-serverless-cache is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create-serverless-cache? +

Yes. Add a rate_limit block to the create-serverless-cache 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 create-serverless-cache completely? +

Set action: deny in the Intercept policy for create-serverless-cache. 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 create-serverless-cache? +

create-serverless-cache 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.