High Risk →

xcomet_evaluate

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 (str...

Part of the Xcomet server.

xcomet_evaluate can trigger actions in Xcomet, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE XCOMET →

Free to start. No card required.

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. PolicyLayer 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "xcomet_evaluate": {
      "limits": [
        {
          "counter": "xcomet_evaluate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Xcomet policy for all 3 tools.

Get this rule live on your own Xcomet server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY XCOMET →

These attack patterns abuse exactly the kind of access xcomet_evaluate gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so xcomet_evaluate only ever does what you allow.

SECURE XCOMET →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the xcomet_evaluate tool do? +

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.

How do I enforce a policy on xcomet_evaluate? +

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

What risk level is xcomet_evaluate? +

xcomet_evaluate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit xcomet_evaluate? +

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

Set action: deny in the PolicyLayer 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.

What MCP server provides xcomet_evaluate? +

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

Enforce policy on every Xcomet tool call.

Deterministic rules across all 3 Xcomet tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.