batch_translate · Localise MCP: Risk & Policy

WHAT IT DOES

What batch_translate does on Localise

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

WHY IT NEEDS A POLICY

Why batch_translate needs a policy

This tool creates assets and writes translation data for multiple locales simultaneously. It is a bulk write operation with no indication of irreversible deletion or financial impact. Misuse could pollute translation data across many locales at once, hence medium severity.

From the tool's definition 'Create an asset and add translations for multiple locales at once' — creates and adds data across multiple locales

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_translate Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "batch_translate": {
      "limits": [
        {
          "counter": "batch_translate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about batch_translate

What does the batch_translate tool do? +

Create an asset and add translations for multiple locales at once. It is categorised as a Write tool in the Localise MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on batch_translate? +

Register the Localise MCP server in PolicyLayer and add a rule for batch_translate: 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 Localise. Nothing to install.

What risk level is batch_translate? +

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

Can I rate-limit batch_translate? +

Yes. Add a rate_limit block to the batch_translate 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 batch_translate completely? +

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

batch_translate is provided by the Localise MCP server (localise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.