Evaluate multiple translation pairs in a batch. This tool processes multiple source-translation pairs and provides aggregate statistics along with individual results. Args: - pairs (array): Array of translation pairs, each with: - source (string): Original source text - translation (s...
Bulk/mass operation — affects multiple targets
Part of the Xcomet MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use xcomet_batch_evaluate to create or modify resources in Xcomet. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call xcomet_batch_evaluate repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Xcomet.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
xcomet_batch_evaluate:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Xcomet policy for all 3 tools.
Agents calling write-class tools like xcomet_batch_evaluate have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Evaluate multiple translation pairs in a batch. This tool processes multiple source-translation pairs and provides aggregate statistics along with individual results. Args: - pairs (array): Array of translation pairs, each with: - source (string): Original source text - translation (string): Translated text - reference (string, optional): Reference translation - source_lang (string, optional): Source language code - target_lang (string, optional): Target language code - response_format ('json' | 'markdown'): Output format (default: 'json') Returns: { "average_score": number, "total_pairs": number, "results": [ { "index": number, "score": number, "error_count": number, "has_critical_errors": boolean } ], "summary": string } Examples: - Evaluate entire translated document - Compare MT system quality across test set - Identify segments needing attention. It is categorised as a Write tool in the Xcomet MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for xcomet_batch_evaluate. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Xcomet MCP server.
xcomet_batch_evaluate 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 xcomet_batch_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_batch_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_batch_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