Medium Risk

create_queue

create_queue

How to control create_queue ↓

What create_queue does on Amazon Translate MCP Server

AI agents use create_queue to create or update resources in Amazon Translate MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon Translate MCP Server environment.

Medium Risk

Why create_queue needs a policy

The tool name 'create_queue' indicates a Write operation—it creates a new resource. Without a description, confidence is reduced, but the action itself is reversible (queues can be deleted). It does not execute arbitrary code, delete data irreversibly, or move money, so Write is the most appropriate category.

From the tool's definition Tool named 'create_queue' with empty description. Based on naming convention and context as an Amazon Translate MCP server, this likely creates a queue resource (e.g., SQS) for batch translation processing.

Documented attack patterns abuse exactly the kind of access create_queue gives an agent:

How to control create_queue

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Translate MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_queue:

policy.json
{
  "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.

  1. Create a free account and register Amazon Translate MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_queue

What does the create_queue tool do? +

create_queue. It is categorised as a Write tool in the Amazon Translate MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_queue? +

Register the Amazon Translate 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 Translate MCP Server. Nothing to install.

What risk level is create_queue? +

create_queue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_queue? +

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.

How do I block create_queue completely? +

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.

What MCP server provides create_queue? +

create_queue is provided by the Amazon Translate MCP Server MCP server (awslabs.amazon-translate-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon Translate MCP Server tool call.

Start from Amazon Translate 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 Translate MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.