watchlist_list_entities

List watched entities from the local founder watchlist.

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/watchlist-list-entities.md

WHAT IT DOES

What watchlist_list_entities does on Nodebench

AI agents call watchlist_list_entities 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 watchlist_list_entities is rated Low

This tool retrieves or queries data from a local watchlist without modifying, deleting, or executing any operations. The verb 'list' and the absence of any modification language confirm it is a read-only operation with minimal security impact.

From the tool's definition Tool name contains 'list' and description states 'List watched entities from the local founder watchlist', indicating data retrieval with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

watchlist_list_entities Allowed

watchlist_list_entities 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": {
    "watchlist_list_entities": {}
  }
}

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 watchlist_list_entities call is checked against it from then on.

FAQ

Questions about watchlist_list_entities

What does the watchlist_list_entities tool do? +

List watched entities from the local founder watchlist. 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 watchlist_list_entities? +

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

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

Can I rate-limit watchlist_list_entities? +

Yes. Add a rate_limit block to the watchlist_list_entities 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 watchlist_list_entities completely? +

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

watchlist_list_entities 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 →