suggest_related

Suggest related items given a root URI (entity://, report://, etc.). PR1 implementation uses the root

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/suggest-related.md

WHAT IT DOES

What suggest_related does on Nodebench

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

This tool queries or retrieves data (related items) based on an input URI with no side effects. It performs a lookup/suggestion operation typical of Read category tools. No evidence of write, execute, destructive, or financial capabilities. Severity is low as suggestion retrieval has minimal blast radius if misused by an AI agent.

From the tool's definition Tool 'suggest_related' retrieves or suggests related items based on a root URI parameter. The description indicates it 'Suggest[s] related items' with no mention of modification, deletion, code execution, or financial operations.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

suggest_related Allowed

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

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

FAQ

Questions about suggest_related

What does the suggest_related tool do? +

Suggest related items given a root URI (entity://, report://, etc.). PR1 implementation uses the root. 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 suggest_related? +

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

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

Can I rate-limit suggest_related? +

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

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

suggest_related 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

suggest_cocktail on Cocktails RAG MCP Server → The MCP Attack Database →

Guides

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