Detect and categorize errors in a translation. This tool focuses on error detection, providing detailed information about translation errors with their severity levels and positions. Args: - source (string): Original source text - translation (string): Translated text to analyze - referen...
Part of the Xcomet MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call xcomet_detect_errors to retrieve information from Xcomet without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though xcomet_detect_errors only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
xcomet_detect_errors:
rules:
- action: allowSee the full Xcomet policy for all 3 tools.
Agents calling read-class tools like xcomet_detect_errors have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Detect and categorize errors in a translation. This tool focuses on error detection, providing detailed information about translation errors with their severity levels and positions. Args: - source (string): Original source text - translation (string): Translated text to analyze - reference (string, optional): Reference translation - min_severity ('minor' | 'major' | 'critical'): Minimum severity to report (default: 'minor') - response_format ('json' | 'markdown'): Output format (default: 'json') Returns: { "total_errors": number, "errors_by_severity": { "minor": number, "major": number, "critical": number }, "errors": [ { "text": string, "start": number, "end": number, "severity": "minor" | "major" | "critical", "suggestion": string | null } ] } Examples: - Find critical errors before publication - Identify areas needing post-editing - Quality gate for MT output. It is categorised as a Read tool in the Xcomet MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for xcomet_detect_errors. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Xcomet MCP server.
xcomet_detect_errors is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the xcomet_detect_errors 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_detect_errors. 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_detect_errors 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