AI agents use create_cluster to create or update resources in Awslabs Amazon Sns Sqs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Awslabs Amazon Sns Sqs environment.
The tool creates a new Aurora MySQL cluster, which is a persistent but reversible infrastructure change. While this is a Write operation (creating new resources), the severity is high because provisioning a database cluster can incur significant AWS costs and creates dependencies that other systems may rely on.
From the tool's definition Tool name 'create_cluster' and description 'Create an Aurora MySQL cluster' indicate creation of a new database resource. This is a Write operation as it creates a new infrastructure component that is reversible (can be deleted).
Documented attack patterns abuse exactly the kind of access create_cluster gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Awslabs Amazon Sns Sqs, and nothing reaches the server without passing your rules. This is the rule we recommend for create_cluster:
{
"version": "1",
"default": "deny",
"tools": {
"create_cluster": {
"limits": [
{
"counter": "create_cluster_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_cluster stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create an Aurora MySQL cluster. It is categorised as a Write tool in the Awslabs Amazon Sns Sqs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Awslabs Amazon Sns Sqs 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 Awslabs Amazon Sns Sqs. 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 Awslabs Amazon Sns Sqs MCP server (awslabs.amazon-sns-sqs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Awslabs Amazon Sns Sqs, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Awslabs Amazon Sns Sqs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.