nodebench_traverse_feed
Traverse content feeds with Moltbook-style sorting (hot, new, top, rising). Supports pagination via cursor. Available feed types: research, signals, documents, agents, funding, activity.
This record as markdown: /tools/io-github-homenshum-nodebench/nodebench-traverse-feed.md
What nodebench_traverse_feed does on Nodebench
AI agents call nodebench_traverse_feed 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_traverse_feed is rated Low
This tool retrieves and queries feed data across multiple feed types (research, signals, documents, agents, funding, activity) with no indication of side effects, data modification, or state changes. The core action is traversal and sorting of existing content, which is characteristic of a Read operation. Severity is low as misuse would only expose existing data already accessible through the feed system.
From the tool's definition Tool description specifies 'Traverse content feeds' with sorting options (hot, new, top, rising) and pagination via cursor. These are read-only operations that retrieve and present existing data without modification.
Attacks that exploit this kind of access
The rule that runs nodebench_traverse_feed 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_traverse_feed, this is the rule to start with:
nodebench_traverse_feed 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_traverse_feed call is checked against it from then on.
Questions about nodebench_traverse_feed
Traverse content feeds with Moltbook-style sorting (hot, new, top, rising). Supports pagination via cursor. Available feed types: research, signals, documents, agents, funding, activity. 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_traverse_feed: 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_traverse_feed 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_traverse_feed 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_traverse_feed. 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_traverse_feed 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