nodebench.activity_timeline
Read the canonical activity ledger for a NodeBench report, including captures, notebook patches, graph clicks, export events, and search/cache decisions.
This record as markdown: /tools/io-github-homenshum-nodebench/nodebench.activity-timeline.md
What nodebench.activity_timeline does on Nodebench
AI agents call nodebench.activity_timeline 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.activity_timeline is rated Low
This tool queries an immutable activity ledger (captures, patches, clicks, events, decisions) without creating, modifying, or deleting data. It is a pure retrieval operation with no side effects or external triggers. Low severity because access to an activity log presents minimal risk even if an AI agent misuses it — it cannot alter state or cause harm beyond information disclosure.
From the tool's definition "Read the canonical activity ledger" — explicit read operation with no modification capability. Retrieves historical log/audit data from a report.
Attacks that exploit this kind of access
The rule that runs nodebench.activity_timeline 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.activity_timeline, this is the rule to start with:
nodebench.activity_timeline 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.activity_timeline call is checked against it from then on.
Questions about nodebench.activity_timeline
Read the canonical activity ledger for a NodeBench report, including captures, notebook patches, graph clicks, export events, and search/cache decisions. 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.activity_timeline: 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.activity_timeline 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.activity_timeline 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.activity_timeline. 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.activity_timeline 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