Retrieve validation trend data from your qualitygate_validate history. Call periodically (e.g. daily or weekly) to spot degrading output quality. Returns daily pass/warn/fail counts, overall pass rate, most common failure reasons ranked by frequency, and check-type distribution (directive_complia...
Part of the Plith MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke qualitygate_trends to trigger processes or run actions in Plith. 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.
qualitygate_trends 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:
qualitygate_trends:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Plith policy for all 14 tools.
Agents calling execute-class tools like qualitygate_trends 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.
qualitygate_trends is one of the high-risk operations in Plith. 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.
Retrieve validation trend data from your qualitygate_validate history. Call periodically (e.g. daily or weekly) to spot degrading output quality. Returns daily pass/warn/fail counts, overall pass rate, most common failure reasons ranked by frequency, and check-type distribution (directive_compliance, schema_validation, code_syntax, tone, factual_claims). Use after running qualitygate_validate regularly to build a meaningful trend. Free — no credits charged.. It is categorised as a Execute tool in the Plith 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 qualitygate_trends. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Plith MCP server.
qualitygate_trends 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 qualitygate_trends 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 qualitygate_trends. 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.
qualitygate_trends is provided by the Plith MCP server (plith/plith). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.