AI agents use create_queue to create or update resources in Amazon Data Processing MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon Data Processing MCP Server environment.
The tool creates a queue, which is a reversible Write operation (queues can be deleted). Without a description, we cannot determine if this is AWS SQS, SNS, or another queue service, but queue creation is a persistent data structure modification. Medium severity reflects potential for misconfiguration or resource exhaustion if an agent creates many queues, but the effect is not destructive and likely reversible.
From the tool's definition Tool name 'create_queue' indicates creation of a queue resource; no description provided to clarify scope or side effects.
Documented attack patterns abuse exactly the kind of access create_queue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Data Processing MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_queue:
{
"version": "1",
"default": "deny",
"tools": {
"create_queue": {
"limits": [
{
"counter": "create_queue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_queue 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_queue. It is categorised as a Write tool in the Amazon Data Processing MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon Data Processing MCP Server MCP server in PolicyLayer and add a rule for create_queue: 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 Data Processing MCP Server. Nothing to install.
create_queue 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_queue 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_queue. 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_queue is provided by the Amazon Data Processing MCP Server MCP server (awslabs.aws-dataprocessing-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Data Processing MCP Server, 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 Amazon Data Processing MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.