track
Add, check, remove, or list tracked entities with one workflow tool. The default path optimizes for watched entities that can feed future nudges and brief artifacts.
This record as markdown: /tools/io-github-homenshum-nodebench/track.md
What track does on Nodebench
AI agents use track 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 track is rated Medium
The tool performs multiple operations including add and remove on tracked entities. Since it can both create and delete tracked entries, the most severe non-destructive interpretation applies — Write — as 'remove' here likely means untracking (reversible) rather than permanent deletion of underlying data.
From the tool's definition 'Add, check, remove, or list tracked entities with one workflow tool'
Attacks that exploit this kind of access
The rule that runs track 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 track, this is the rule to start with:
track 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 track call is checked against it from then on.
Questions about track
Add, check, remove, or list tracked entities with one workflow tool. The default path optimizes for watched entities that can feed future nudges and brief artifacts. 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 track: 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.
track 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 track 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 track. 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.
track 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