list_learnings
[DEPRECATED: Use search_all_knowledge instead] List stored learnings. PREFER search_all_knowledge for unified knowledge search across learnings, recon findings, and gaps.
This record as markdown: /tools/io-github-homenshum-nodebench/list-learnings.md
What list_learnings does on Nodebench
AI agents call list_learnings 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 list_learnings is rated Low
This tool queries or retrieves stored learnings with no side effects. Despite being deprecated, it remains a data retrieval operation that does not create, modify, delete, or execute any operations. The low severity reflects minimal blast radius—listing learnings poses no risk of data loss, financial impact, or system compromise even if misused by an agent.
From the tool's definition Tool description states 'List stored learnings' and is explicitly deprecated in favor of a search function, indicating it retrieves data without modification. The verb 'list' is characteristic of read-only operations.
Attacks that exploit this kind of access
The rule that runs list_learnings 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 list_learnings, this is the rule to start with:
list_learnings 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 list_learnings call is checked against it from then on.
Questions about list_learnings
[DEPRECATED: Use search_all_knowledge instead] List stored learnings. PREFER search_all_knowledge for unified knowledge search across learnings, recon findings, and gaps. 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 list_learnings: 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.
list_learnings 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 list_learnings 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 list_learnings. 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.
list_learnings 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