scan_webmcp_origin

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/scan-webmcp-origin.md

WHAT IT DOES

What scan_webmcp_origin does on Nodebench

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

This tool queries a WebMCP-enabled site to inventory its available tools and stores the results locally. It has no side effects on the remote server or local system beyond non-destructive caching. The manifest discovery and caching are read-only operations. Severity is low because the tool merely retrieves and stores metadata about tool availability with no ability to execute those tools or modify their behavior.

From the tool's definition Tool performs 'one-shot scan' to 'discover tools, cache the manifest, and disconnect' without modifying or deleting data. Core operations are 'connect', 'discover', and 'cache' — purely retrieval and local caching activities.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

scan_webmcp_origin Allowed

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

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

FAQ

Questions about scan_webmcp_origin

What does the scan_webmcp_origin tool do? +

One-shot scan: connect to a WebMCP-enabled site, discover tools, cache the manifest, and disconnect. Useful for inventorying WebMCP tools without keeping a browser open. Results are cached to ~/.nodebench/webmcp_cache/. 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 scan_webmcp_origin? +

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

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

Can I rate-limit scan_webmcp_origin? +

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

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

scan_webmcp_origin 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 →