distribution_surface_scan

Scan which distribution surfaces are actually ready right now.

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

Questions about distribution_surface_scan

What does the distribution_surface_scan tool do? +

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.

How do I enforce a policy on distribution_surface_scan? +

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.

What risk level is distribution_surface_scan? +

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

Can I rate-limit distribution_surface_scan? +

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.

How do I block distribution_surface_scan completely? +

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.

What MCP server provides distribution_surface_scan? +

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.

Across the catalogue

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