list_webmcp_tools
List all tools discovered from connected WebMCP origins. Shows tool names, descriptions, and input schemas. Optionally filter by origin.
This record as markdown: /tools/io-github-homenshum-nodebench/list-webmcp-tools.md
What list_webmcp_tools does on Nodebench
AI agents call list_webmcp_tools 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 list_webmcp_tools is rated Low
This tool retrieves and displays metadata about available tools from WebMCP origins. It has no side effects, performs no modifications, executes no code, deletes nothing, and involves no financial transactions. The blast radius of misuse is minimal—an agent could discover tool names and schemas but cannot invoke them or cause harm through this tool alone. It is clearly a Read operation.
From the tool's definition Tool name 'list_webmcp_tools' and description 'List all tools discovered from connected WebMCP origins' indicate a retrieval operation. The verb 'List' and 'Shows' confirm it queries/displays existing data without modification or execution.
Attacks that exploit this kind of access
The rule that runs list_webmcp_tools 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 list_webmcp_tools, this is the rule to start with:
list_webmcp_tools 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 list_webmcp_tools call is checked against it from then on.
Questions about list_webmcp_tools
List all tools discovered from connected WebMCP origins. Shows tool names, descriptions, and input schemas. Optionally filter by origin. 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 list_webmcp_tools: 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.
list_webmcp_tools 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 list_webmcp_tools 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 list_webmcp_tools. 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.
list_webmcp_tools 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