Create an Aurora MySQL cluster
AI agents use create_cluster to create or update resources in Amazon ElastiCache Memcached MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon ElastiCache Memcached MCP Server environment.
Creating a cluster is a Write operation because it creates a new resource whose effects can be reversed (the cluster can be deleted). However, the severity is elevated to 'high' because cluster creation provisions compute and storage resources that incur ongoing AWS costs and require cleanup to avoid unexpected charges.
From the tool's definition Tool name: 'create_cluster'; description: 'Create an Aurora MySQL cluster'. The action is creation of a new database cluster resource in AWS, which is a reversible write operation that modifies infrastructure state.
Attacks that exploit this kind of access
Create an Aurora MySQL cluster. It is categorised as a Write tool in the Amazon ElastiCache Memcached MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon ElastiCache Memcached MCP Server MCP server in PolicyLayer and add a rule for create_cluster: 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 Amazon ElastiCache Memcached MCP Server. Nothing to install.
create_cluster 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_cluster 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_cluster. 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_cluster is provided by the Amazon ElastiCache Memcached MCP Server MCP server (awslabs.memcached-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.