Lists all WebMCP tools the page exposes.
AI agents call list_webmcp_tools to retrieve information from Chrome Devtools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available tools exposed by a page, similar to introspection or discovery. It does not modify, execute, or delete anything. The fact that it operates in a browser automation context does not elevate its risk; it remains a read-only information retrieval operation. Severity is low because the information disclosed is about available tools, not sensitive user data or system state.
From the tool's definition Tool name and description indicate it 'Lists all WebMCP tools' — a query/inspection operation with no side effects. Analogous to 'list' or 'get' operations.
Attacks that exploit this kind of access
Lists all WebMCP tools the page exposes. It is categorised as a Read tool in the Chrome Devtools MCP Server, which means it retrieves data without modifying state.
Register the Chrome Devtools 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 Chrome Devtools. 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 Chrome Devtools MCP server (shivamprasad99/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →