AI agents use list_move 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.
Moving an element from one list to another is a reversible write operation (the element is relocated, not deleted). However, the description is vague and doesn't clearly fit the SNS/SQS context, which lowers confidence. It likely refers to moving queue or topic elements between lists/groups, which is a write-level action with moderate blast radius if misused.
From the tool's definition 'Move element from one list to another' — moves data between lists, implying a write/modify operation
Documented attack patterns abuse exactly the kind of access list_move 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 list_move:
{
"version": "1",
"default": "deny",
"tools": {
"list_move": {
"limits": [
{
"counter": "list_move_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}list_move 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.
Move element from one list to another. 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 list_move: 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.
list_move 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 list_move 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 list_move. 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.
list_move 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.