nodebench.report_export_preview
Prepare a reviewable NodeBench report export. Returns mapped contacts, companies, interactions, follow-ups, claims, and sources before any completed export.
This record as markdown: /tools/io-github-homenshum-nodebench/nodebench.report-export-preview.md
What nodebench.report_export_preview does on Nodebench
AI agents call nodebench.report_export_preview 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 nodebench.report_export_preview is rated Low
The tool prepares a preview of data for review before an actual export is completed. It only retrieves and returns data (contacts, companies, interactions, etc.) without creating, modifying, or deleting anything. The phrase 'before any completed export' confirms no persistent side effects occur.
From the tool's definition 'Prepare a reviewable NodeBench report export. Returns mapped contacts, companies, interactions, follow-ups, claims, and sources before any completed export.'
Attacks that exploit this kind of access
The rule that runs nodebench.report_export_preview 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 nodebench.report_export_preview, this is the rule to start with:
nodebench.report_export_preview 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 nodebench.report_export_preview call is checked against it from then on.
Questions about nodebench.report_export_preview
Prepare a reviewable NodeBench report export. Returns mapped contacts, companies, interactions, follow-ups, claims, and sources before any completed export. 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 nodebench.report_export_preview: 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.
nodebench.report_export_preview 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 nodebench.report_export_preview 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 nodebench.report_export_preview. 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.
nodebench.report_export_preview 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