AI agents use cache_cas 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.
This tool performs a write operation that creates or modifies data. While CAS is a reversible operation (the value can be changed again), it modifies state and could have side effects depending on what system it's writing to. Given the server context (SNS/SQS messaging), this could potentially modify message attributes, queue configurations, or cached state.
From the tool's definition Tool description states 'Set a value using CAS (Check And Set)', which indicates a write operation that modifies data. CAS is a conditional write operation that atomically checks a value and then sets it if the condition is met.
Documented attack patterns abuse exactly the kind of access cache_cas 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 cache_cas:
{
"version": "1",
"default": "deny",
"tools": {
"cache_cas": {
"limits": [
{
"counter": "cache_cas_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}cache_cas 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.
Set a value using CAS (Check And Set). 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 cache_cas: 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.
cache_cas 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 cache_cas 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 cache_cas. 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.
cache_cas 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.