nb_get_feed_items
Get public research feed items surfaced on Home.
This record as markdown: /tools/io-github-homenshum-nodebench/nb-get-feed-items.md
What nb_get_feed_items does on Nodebench
AI agents call nb_get_feed_items 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 nb_get_feed_items is rated Low
This tool queries and retrieves public feed items without side effects. The 'get' verb and description emphasize retrieval of existing data. No mention of creation, modification, deletion, or execution of operations. The data is explicitly public, further reducing risk. This is a straightforward Read operation.
From the tool's definition Tool name contains 'get' and description states 'Get public research feed items' — retrieves data with no modification capability.
Attacks that exploit this kind of access
The rule that runs nb_get_feed_items 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 nb_get_feed_items, this is the rule to start with:
nb_get_feed_items 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 nb_get_feed_items call is checked against it from then on.
Questions about nb_get_feed_items
Get public research feed items surfaced on Home. 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 nb_get_feed_items: 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.
nb_get_feed_items 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 nb_get_feed_items 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 nb_get_feed_items. 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.
nb_get_feed_items 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