list_shared_context_peers

List peers by product, workspace, role, surface, capability, or scope.

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-shared-context-peers.md

What list_shared_context_peers does on Nodebench

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

This tool retrieves and lists peer entities based on provided filters. The verb 'list' and absence of any modification, deletion, or execution language confirm this is a read-only operation with no side effects. Severity is low as it only returns reference data about peers/context without exposing sensitive operations.

From the tool's definition Tool name 'list_shared_context_peers' with description 'List peers by product, workspace, role, surface, capability, or scope' indicates a query/retrieval operation that returns filtered peer information without modifying data.

Questions about list_shared_context_peers

What does the list_shared_context_peers tool do? +

List peers by product, workspace, role, surface, capability, or scope. 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_shared_context_peers? +

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

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

Can I rate-limit list_shared_context_peers? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nodebench's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.