Upload a source file to create translation jobs in a Phrase TMS project. One job is created per target language. Common supported formats: XLIFF, PO, DOCX, XLSX, HTML, JSON, SRT, and most standard content formats. Provide either file_path (host filesystem path, for local MCP server use) or file_c...
AI agents use tms_create_job_from_file 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.
This tool creates new translation jobs in a Phrase TMS project by uploading source files. While the creation is reversible (jobs can be deleted), the ability to bulk-create translation jobs with arbitrary file content could have significant downstream effects on project workflows. An AI agent misusing this could flood a project with unwanted jobs, disrupt translation pipelines, or expose sensitive source content.
From the tool's definition The tool description explicitly states it 'Upload[s] a source file to create translation jobs' using a POST endpoint. The action creates new translation job resources in the TMS project, which is a reversible write operation.
Attacks that exploit this kind of access
Upload a source file to create translation jobs in a Phrase TMS project. One job is created per target language. Common supported formats: XLIFF, PO, DOCX, XLSX, HTML, JSON, SRT, and most standard content formats. Provide either file_path (host filesystem path, for local MCP server use) or file_content + file_name (base64-encoded file bytes, for Claude Desktop uploaded files). (POST /api2/v1/projects/{projectUid}/jobs). 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.
Register the Phrase MCP server in PolicyLayer and add a rule for tms_create_job_from_file: 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.
tms_create_job_from_file 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 tms_create_job_from_file 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 tms_create_job_from_file. 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.
tms_create_job_from_file 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.
tms_create_job_from_file is one line of Phrase's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →