get_distribution_surfaces

Inspect NodeBench MCP distribution surfaces: npm/npx, installer, plugin configs, Smithery, and shared web review surfaces.

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/get-distribution-surfaces.md

WHAT IT DOES

What get_distribution_surfaces does on Nodebench

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

This tool retrieves and examines configuration and metadata about how NodeBench is distributed across various platforms (npm/npx, installers, plugin configs, Smithery, web surfaces). There is no evidence of creation, modification, deletion, code execution, or financial impact. The tool is purely informational and has no side effects beyond returning inspection results.

From the tool's definition Tool name 'get_distribution_surfaces' and description 'Inspect NodeBench MCP distribution surfaces' indicate data retrieval and inspection only.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_distribution_surfaces Allowed

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

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

FAQ

Questions about get_distribution_surfaces

What does the get_distribution_surfaces tool do? +

Inspect NodeBench MCP distribution surfaces: npm/npx, installer, plugin configs, Smithery, and shared web review surfaces. 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 get_distribution_surfaces? +

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

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

Can I rate-limit get_distribution_surfaces? +

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

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

get_distribution_surfaces 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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