AI agents use setup 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.
Without a description, classification confidence is reduced. However, 'setup' in the context of AWS services typically involves creating or configuring resources (Write category). The high severity reflects that misconfigured setup on AWS Translate could affect translation pipelines, custom terminology, or batch processing. Given the empty description, confidence is moderate (0.6) rather than high.
From the tool's definition Tool named 'setup' on Amazon Translate MCP Server with empty description; sibling tools show patterns of configuration/management operations (add_inline_policy, add_user_to_group, add_attachments_to_set).
Documented attack patterns abuse exactly the kind of access setup gives an agent:
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 setup:
{
"version": "1",
"default": "deny",
"tools": {
"setup": {
"limits": [
{
"counter": "setup_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}setup 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.
setup. 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.
Register the Amazon Translate MCP Server MCP server in PolicyLayer and add a rule for setup: 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.
setup 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 setup 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 setup. 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.
setup 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.
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.