AI agents use resolve_support_case 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.
The tool name suggests it modifies support case status (likely from open to resolved), which is a reversible state change. While the empty description creates uncertainty about exact behavior, resolving a case is Write-level severity as it changes data state but is theoretically reversible (cases can be reopened). Confidence is lowered due to empty description and apparent misalignment with the stated server purpose.
From the tool's definition Tool name 'resolve_support_case' indicates closing/modifying a support case. The server description mentions 'text translation, custom terminology management, and batch translation processing,' but this tool appears misaligned or mislabeled.
Documented attack patterns abuse exactly the kind of access resolve_support_case 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 resolve_support_case:
{
"version": "1",
"default": "deny",
"tools": {
"resolve_support_case": {
"limits": [
{
"counter": "resolve_support_case_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}resolve_support_case 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.
resolve_support_case. 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 resolve_support_case: 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.
resolve_support_case 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 resolve_support_case 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 resolve_support_case. 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.
resolve_support_case 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.