convex_export_sarif
Export stored audit results as SARIF 2.1.0 JSON. SARIF is the industry standard for static analysis results — integrates with GitHub Code Scanning, VS Code Problems panel, and CI pipelines. Outputs file:line locations, severity levels, and fix suggestions.
This record as markdown: /tools/io-github-homenshum-nodebench/convex-export-sarif.md
What convex_export_sarif does on Nodebench
AI agents call convex_export_sarif 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.
Why convex_export_sarif is rated Low
This tool reads and exports previously stored audit results in SARIF format. It does not modify, delete, or execute anything — it retrieves existing data and formats it for output. The blast radius is low since it only reads stored results.
From the tool's definition Export stored audit results as SARIF 2.1.0 JSON
Attacks that exploit this kind of access
The rule that runs convex_export_sarif 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_export_sarif, this is the rule to start with:
convex_export_sarif is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every convex_export_sarif call is checked against it from then on.
Questions about convex_export_sarif
Export stored audit results as SARIF 2.1.0 JSON. SARIF is the industry standard for static analysis results — integrates with GitHub Code Scanning, VS Code Problems panel, and CI pipelines. Outputs file:line locations, severity levels, and fix suggestions. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for convex_export_sarif: 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.
convex_export_sarif 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 convex_export_sarif 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 convex_export_sarif. 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.
convex_export_sarif 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.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue