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): Tran...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Xcomet server.
Free to start. No card required.
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. PolicyLayer'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.
{
"version": "1",
"default": "deny",
"tools": {
"xcomet_batch_evaluate": {
"limits": [
{
"counter": "xcomet_batch_evaluate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Xcomet policy for all 3 tools.
These attack patterns abuse exactly the kind of access xcomet_batch_evaluate gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
Register the Xcomet MCP server in PolicyLayer and add a rule for xcomet_batch_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.
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 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 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). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
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.