create-serverless-cache
AI agents use create-serverless-cache to create or update resources in Awslabs Valkey — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Awslabs Valkey environment.
The tool creates a new serverless cache instance, which is a reversible infrastructure provisioning action typical of Write operations. This is not Destructive because the action is not irreversible—the cache can be deleted or modified. However, it has high severity because misconfiguration or accidental creation could consume cloud resources and incur costs, and the empty description limits confidence to 0.75.
From the tool's definition Tool name 'create-serverless-cache' indicates creation of a new AWS ElastiCache resource. The 'create' verb combined with 'cache' (a cloud infrastructure resource) indicates a Write operation that provisions infrastructure.
Attacks that exploit this kind of access
create-serverless-cache. It is categorised as a Write tool in the Awslabs Valkey MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for create-serverless-cache: 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.
create-serverless-cache 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 create-serverless-cache 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.
Set action: deny in the PolicyLayer 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.
create-serverless-cache 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.