Evaluate the quality of a translation using xCOMET model. This tool analyzes a source text and its translation, providing: - A quality score between 0 and 1 (higher is better) - Detected error spans with severity levels (minor/major/critical) - A human-readable quality summary Args: - source ...
Part of the Xcomet MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke xcomet_evaluate to trigger processes or run actions in Xcomet. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
xcomet_evaluate can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
xcomet_evaluate:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Xcomet policy for all 3 tools.
Agents calling execute-class tools like xcomet_evaluate have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
xcomet_evaluate is one of the high-risk operations in Xcomet. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Evaluate the quality of a translation using xCOMET model. This tool analyzes a source text and its translation, providing: - A quality score between 0 and 1 (higher is better) - Detected error spans with severity levels (minor/major/critical) - A human-readable quality summary Args: - source (string): Original source text to translate from - translation (string): Translated text to evaluate - reference (string, optional): Reference translation for comparison - source_lang (string, optional): Source language code (ISO 639-1) - target_lang (string, optional): Target language code (ISO 639-1) - response_format ('json' | 'markdown'): Output format (default: 'json') Returns: For JSON format: { "score": number, // Quality score 0-1 "errors": [ // Detected errors { "text": string, "start": number, "end": number, "severity": "minor" | "major" | "critical" } ], "summary": string // Human-readable summary } Examples: - Evaluate EN→JA translation quality - Check if MT output needs post-editing - Compare translation against reference. It is categorised as a Execute tool in the Xcomet MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for xcomet_evaluate. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Xcomet MCP server.
xcomet_evaluate 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 xcomet_evaluate rule in your Intercept 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 Intercept policy for xcomet_evaluate. 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.
xcomet_evaluate is provided by the Xcomet MCP server (xcomet-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept