pull_shared_context

Pull shared-context packets by type, producer, scope, workspace, status, or subject substring.

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

WHAT IT DOES

What pull_shared_context does on Nodebench

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

This tool queries and retrieves shared-context data based on various filter criteria. It performs no modification, deletion, execution, or financial operations. The operation is purely informational — pulling existing data packets with no side effects. This is a classic Read category tool.

From the tool's definition Tool description states 'Pull shared-context packets by type, producer, scope, workspace, status, or subject substring' — this is a retrieval/query operation with filtering parameters.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pull_shared_context Allowed

pull_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": {
    "pull_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 pull_shared_context call is checked against it from then on.

FAQ

Questions about pull_shared_context

What does the pull_shared_context tool do? +

Pull shared-context packets by type, producer, scope, workspace, status, or subject substring. 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 pull_shared_context? +

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

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

Can I rate-limit pull_shared_context? +

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

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

pull_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

The MCP Attack Database →

Guides

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