distribution_surface_scan
Scan which distribution surfaces are actually ready right now.
This record as markdown: /tools/io-github-homenshum-nodebench/distribution-surface-scan.md
What distribution_surface_scan does on Nodebench
AI agents call distribution_surface_scan 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 distribution_surface_scan is rated Low
This tool performs a read-only assessment or query of distribution surface readiness status. The verb 'scan' in this context means to examine or check current state, and there is no indication of side effects, modifications, creation, deletion, or execution of external operations. The tool simply returns information about the current state of distribution surfaces.
From the tool's definition The tool name includes 'scan' and the description states 'which distribution surfaces are actually ready right now', indicating a query or status check operation that retrieves information about the state of distribution surfaces without modifying them.
Attacks that exploit this kind of access
The rule that runs distribution_surface_scan 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 distribution_surface_scan, this is the rule to start with:
distribution_surface_scan is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every distribution_surface_scan call is checked against it from then on.
Questions about distribution_surface_scan
Scan which distribution surfaces are actually ready right now. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for distribution_surface_scan: 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.
distribution_surface_scan is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the distribution_surface_scan 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.
Set action: deny in the PolicyLayer policy for distribution_surface_scan. 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.
distribution_surface_scan 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.
This server
Across the catalogue