trigger_batch_translation · AWS IoT SiteWise MCP Server MCP

WHAT IT DOES

What trigger_batch_translation does on AWS IoT SiteWise MCP Server

AI agents invoke trigger_batch_translation to trigger actions in AWS IoT SiteWise MCP Server. 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 IT NEEDS A POLICY

Why trigger_batch_translation needs a policy

Triggering a batch translation operation qualifies as Execute because it initiates an external operation whose side effects depend on arguments and configuration (what gets translated, where results go, error handling). Without a description, confidence is moderate (0.72).

From the tool's definition Tool name 'trigger_batch_translation' indicates initiation of a batch operation. The verb 'trigger' suggests active invocation of an external process or operation whose effects depend on runtime execution and configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trigger_batch_translation Rate-limited

trigger_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "trigger_batch_translation": {
      "limits": [
        {
          "counter": "trigger_batch_translation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches AWS IoT SiteWise MCP Server, so you can run agents against it safely.

FAQ

Questions about trigger_batch_translation

What does the trigger_batch_translation tool do? +

trigger_batch_translation. It is categorised as a Execute tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on trigger_batch_translation? +

Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for trigger_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 IoT SiteWise MCP Server. Nothing to install.

What risk level is trigger_batch_translation? +

trigger_batch_translation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit trigger_batch_translation? +

Yes. Add a rate_limit block to the trigger_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.

How do I block trigger_batch_translation completely? +

Set action: deny in the PolicyLayer policy for trigger_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.

What MCP server provides trigger_batch_translation? +

trigger_batch_translation is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.