sync_report
Push a report artifact from Claude Code into NodeBench AI. The report is saved locally and published as a shared-context packet for the web app to consume.
This record as markdown: /tools/io-github-homenshum-nodebench/sync-report.md
What sync_report does on Nodebench
AI agents use sync_report to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.
Why sync_report is rated Medium
The tool creates/saves a report artifact and publishes it as a shared-context packet. This is a write operation — it creates new data both locally and in the web app context. It does not delete or irreversibly overwrite data, execute code, or involve financial transactions. Severity is medium because it writes potentially sensitive report data to a shared context accessible by other systems/users.
From the tool's definition Push a report artifact...The report is saved locally and published as a shared-context packet
Attacks that exploit this kind of access
The rule that runs sync_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 sync_report, this is the rule to start with:
sync_report stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 sync_report call is checked against it from then on.
Questions about sync_report
Push a report artifact from Claude Code into NodeBench AI. The report is saved locally and published as a shared-context packet for the web app to consume. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nodebench MCP server in PolicyLayer and add a rule for sync_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.
sync_report is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sync_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.
Set action: deny in the PolicyLayer policy for sync_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.
sync_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.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue