tms_set_job_status · Phrase MCP: Risk & Policy

WHAT IT DOES

What tms_set_job_status does on Phrase

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

WHY IT NEEDS A POLICY

Why tms_set_job_status needs a policy

The tool modifies job status in the Phrase TMS system, which is a reversible state change (job status can typically be changed back to a previous state). This is a write operation rather than destructive since it does not irreversibly delete or permanently destroy data.

From the tool's definition Tool description explicitly states 'This operation mutates data' and uses POST method to set job status via /api2/v1/projects/{projectUid}/jobs/{jobUid}/setStatus endpoint.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tms_set_job_status Rate-limited

tms_set_job_status 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": {
    "tms_set_job_status": {
      "limits": [
        {
          "counter": "tms_set_job_status_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 Phrase, so you can run agents against it safely.

FAQ

Questions about tms_set_job_status

What does the tms_set_job_status tool do? +

Set Phrase TMS job status (POST /api2/v1/projects/{projectUid}/jobs/{jobUid}/setStatus). This operation mutates data. It is categorised as a Write tool in the Phrase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on tms_set_job_status? +

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

What risk level is tms_set_job_status? +

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

Can I rate-limit tms_set_job_status? +

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

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

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