convex_quality_gate · Nodebench MCP: Risk & Policy

WHAT IT DOES

What convex_quality_gate does on Nodebench

AI agents invoke convex_quality_gate to trigger actions in Nodebench. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why convex_quality_gate needs a policy

This tool executes a quality gate process with configurable parameters against audit results. While it doesn't directly modify data (Write) or delete it (Destructive), 'Run' clearly indicates code/process execution. The effects depend on configuration and the audit data present, making it Execute rather than Read.

From the tool's definition Tool description states "Run a configurable quality gate" which indicates execution of a process/workflow. The comparison to SonarQube (a code quality analysis tool) suggests this executes automated validation/analysis logic against stored data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

convex_quality_gate Rate-limited

convex_quality_gate stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "convex_quality_gate": {
      "limits": [
        {
          "counter": "convex_quality_gate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nodebench, so you can run agents against it safely.

FAQ

Questions about convex_quality_gate

What does the convex_quality_gate tool do? +

Run a configurable quality gate across all stored audit results. Like SonarQube. It is categorised as a Execute tool in the Nodebench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on convex_quality_gate? +

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

What risk level is convex_quality_gate? +

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

Can I rate-limit convex_quality_gate? +

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

Set action: deny in the PolicyLayer policy for convex_quality_gate. 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 convex_quality_gate? +

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