nb_review_shared_context

Inspect shared-context peers, packets, and handoffs.

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/nb-review-shared-context.md

WHAT IT DOES

What nb_review_shared_context does on Nodebench

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

This tool retrieves and examines shared context information (peers, packets, handoffs) without creating, modifying, deleting, or executing any operations. It is purely a read/query operation with no side effects or blast radius if misused by an agent.

From the tool's definition The tool name includes 'review' and the description states 'Inspect shared-context peers, packets, and handoffs.' The verb 'Inspect' indicates passive observation and data retrieval with no modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

nb_review_shared_context Allowed

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

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

FAQ

Questions about nb_review_shared_context

What does the nb_review_shared_context tool do? +

Inspect shared-context peers, packets, and handoffs. 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 nb_review_shared_context? +

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

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

Can I rate-limit nb_review_shared_context? +

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

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

nb_review_shared_context 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

review_changes on MCP Server PR Pilot → The MCP Attack Database →

Guides

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