list_stale_packets

List memory blocks and packets that need refresh.

SERVERNodebench SOURCEnodebench-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/list-stale-packets.md

WHAT IT DOES

What list_stale_packets does on Nodebench

AI agents call list_stale_packets 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.

RISK

Why list_stale_packets is rated Low

This tool retrieves or queries information about stale memory blocks and packets without modifying or deleting them. It is a diagnostic read operation that supports monitoring and decision-making, not data manipulation. The low severity reflects minimal blast radius—listing data poses no risk of unintended data loss or system damage if misused by an AI agent.

From the tool's definition Tool name 'list_stale_packets' and description 'List memory blocks and packets that need refresh' indicate a retrieval/query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_stale_packets 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_stale_packets, this is the rule to start with:

list_stale_packets Allowed

list_stale_packets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_stale_packets": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every list_stale_packets call is checked against it from then on.

FAQ

Questions about list_stale_packets

What does the list_stale_packets tool do? +

List memory blocks and packets that need refresh. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_stale_packets? +

Register the Nodebench MCP server in PolicyLayer and add a rule for list_stale_packets: 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.

What risk level is list_stale_packets? +

list_stale_packets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_stale_packets? +

Yes. Add a rate_limit block to the list_stale_packets 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.

How do I block list_stale_packets completely? +

Set action: deny in the PolicyLayer policy for list_stale_packets. 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.

What MCP server provides list_stale_packets? +

list_stale_packets 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.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →