check_webmcp_setup

Check WebMCP prerequisites: Playwright installation, Chromium browser availability, and any cached origin data. Returns setup instructions if anything is missing.

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/check-webmcp-setup.md

WHAT IT DOES

What check_webmcp_setup does on Nodebench

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

This is a diagnostic/inspection tool that verifies installation status and availability of dependencies. It performs no write operations, executes no code or external systems, and does not delete or move data. The sole action is reading system state and returning informational output.

From the tool's definition Tool checks prerequisites and returns status/setup instructions ("Check WebMCP prerequisites", "Returns setup instructions") — it queries system state without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_webmcp_setup Allowed

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

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

FAQ

Questions about check_webmcp_setup

What does the check_webmcp_setup tool do? +

Check WebMCP prerequisites: Playwright installation, Chromium browser availability, and any cached origin data. Returns setup instructions if anything is missing. 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 check_webmcp_setup? +

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

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

Can I rate-limit check_webmcp_setup? +

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

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

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