export_audit_report

Export a session activity log as formatted markdown for pull request reports,

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/export-audit-report.md

WHAT IT DOES

What export_audit_report does on Nodebench

AI agents call export_audit_report 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 export_audit_report is rated Low

The tool reads/retrieves an existing session activity log and formats it as markdown output. It does not modify, delete, or execute anything — it is a reporting/export operation with no side effects. Severity is low as misuse would only expose session activity logs.

From the tool's definition Export a session activity log as formatted markdown for pull request reports

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs export_audit_report 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 export_audit_report, this is the rule to start with:

export_audit_report Allowed

export_audit_report 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": {
    "export_audit_report": {}
  }
}

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 export_audit_report call is checked against it from then on.

FAQ

Questions about export_audit_report

What does the export_audit_report tool do? +

Export a session activity log as formatted markdown for pull request reports,. 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 export_audit_report? +

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

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

Can I rate-limit export_audit_report? +

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

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

export_audit_report 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 →