convex_audit_diff

Compare the latest audit run against the previous run to show new issues, fixed issues, and trend direction (improving/stable/degrading). Like SonarQube

SERVERNodebench SOURCEnodebench-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/convex-audit-diff.md

WHAT IT DOES

What convex_audit_diff does on Nodebench

AI agents call convex_audit_diff to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why convex_audit_diff is rated Low

This tool reads and compares existing audit results to surface differences and trends. It does not modify, delete, or execute anything — purely a diff/reporting operation analogous to SonarQube's comparison view.

From the tool's definition Compare the latest audit run against the previous run to show new issues, fixed issues, and trend direction

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs convex_audit_diff safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For convex_audit_diff, this is the rule to start with:

convex_audit_diff Allowed

convex_audit_diff is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "convex_audit_diff": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every convex_audit_diff call is checked against it from then on.

FAQ

Questions about convex_audit_diff

What does the convex_audit_diff tool do? +

Compare the latest audit run against the previous run to show new issues, fixed issues, and trend direction (improving/stable/degrading). Like SonarQube. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on convex_audit_diff? +

Register the Nodebench MCP server in PolicyLayer and add a rule for convex_audit_diff: 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_audit_diff? +

convex_audit_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit convex_audit_diff? +

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

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

convex_audit_diff 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.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →