Trigger asynchronous generation of the translated (target) file for a TMS job. Returns an asyncRequest object with an id field. The file is NOT immediately available. Next: call tms_get_async_request with the returned id and poll until status = COMPLETED, then call tms_download_target_file_by_asy...
AI agents invoke tms_download_target_file_async to trigger actions in Phrase. 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.
This tool triggers an asynchronous operation (file generation) on the server side. It does not simply read existing data nor create/modify user data directly — it initiates a background process. The PUT method and 'trigger' language indicate an execution action rather than a simple read or write.
From the tool's definition Trigger asynchronous generation of the translated (target) file for a TMS job. Returns an asyncRequest object with an id field.
Attacks that exploit this kind of access
Trigger asynchronous generation of the translated (target) file for a TMS job. Returns an asyncRequest object with an id field. The file is NOT immediately available. Next: call tms_get_async_request with the returned id and poll until status = COMPLETED, then call tms_download_target_file_by_async_request to retrieve the file. (PUT /api2/v3/projects/{projectUid}/jobs/{jobUid}/targetFile). It is categorised as a Execute tool in the Phrase MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Phrase MCP server in PolicyLayer and add a rule for tms_download_target_file_async: 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_download_target_file_async is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the tms_download_target_file_async 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_download_target_file_async. 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_download_target_file_async 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →