This record as markdown: /tools/aws/start-batch-translation.md
What start_batch_translation does on AWS
AI agents invoke start_batch_translation to trigger actions in AWS. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why start_batch_translation is rated High
Batch translation jobs execute external operations (likely AWS Translate or similar) whose effects depend on arguments (input data, target languages, parameters). This is an Execute action rather than Read (would be 'get_translation' or 'list_jobs'), Write (reversible creation), or Destructive.
From the tool's definition Tool name 'start_batch_translation' suggests it initiates a batch operation; sibling tools like 'analyze_batch_translation_errors' confirm a translation service context. The description is empty, limiting precise classification.
Attacks that exploit this kind of access
The rule that runs start_batch_translation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For start_batch_translation, this is the rule to start with:
start_batch_translation stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every start_batch_translation call is checked against it from then on.
Questions about start_batch_translation
start_batch_translation is a execute tool on the AWS MCP server. It is categorised as a Execute tool in the AWS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS MCP server in PolicyLayer and add a rule for start_batch_translation: 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 AWS. Nothing to install.
start_batch_translation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_batch_translation 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 start_batch_translation. 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.
start_batch_translation is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AWS, and thousands of servers like it.
This server
Across the catalogue