Trigger an asynchronous quality evaluation against a Quality Profile for the selected TMS job parts. Job parts must be in the same project. Returns an async action descriptor; poll its status with tms_get_async_request. (POST /api2/v1/qualityProfiles/evaluate)
AI agents invoke tms_evaluate_quality_profile 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.
While named 'evaluate', this is not a simple read operation. It actively triggers execution of a quality profile evaluation process on selected TMS job parts, which is a remote operation with side effects. It returns an async action descriptor requiring polling, confirming it launches a background process. This fits Execute (runs external operations whose effects depend on arguments) rather than Read.
From the tool's definition Trigger an asynchronous quality evaluation...Returns an async action descriptor. The verb 'Trigger' combined with 'asynchronous' execution that must be polled indicates this invokes a side-effecting operation that executes external logic (quality evaluation)…
Attacks that exploit this kind of access
Trigger an asynchronous quality evaluation against a Quality Profile for the selected TMS job parts. Job parts must be in the same project. Returns an async action descriptor; poll its status with tms_get_async_request. (POST /api2/v1/qualityProfiles/evaluate). 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_evaluate_quality_profile: 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_evaluate_quality_profile 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_evaluate_quality_profile 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_evaluate_quality_profile. 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_evaluate_quality_profile 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 →