browser_verify_list_visible

A read tool on the Playwright MCP server.

SERVERPlaywright SOURCEhanato238/playwright-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/hanato238-playwright-mcp/browser-verify-list-visible.md

What browser_verify_list_visible does on Playwright

AI agents call browser_verify_list_visible to retrieve information from Playwright without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why browser_verify_list_visible is rated Low

The verb 'verify' combined with 'list_visible' most naturally maps to querying or checking the state of DOM elements—a read-only operation with no side effects. While the description is empty (lowering confidence slightly), the naming pattern and context among related browser automation tools support classification as a Read operation with low severity due to its passive, informational nature.

From the tool's definition Tool name 'browser_verify_list_visible' suggests inspection/verification of visible list elements on a webpage. The 'verify' prefix indicates a query or assertion operation rather than modification.

Questions about browser_verify_list_visible

What does the browser_verify_list_visible tool do? +

browser_verify_list_visible is a read tool on the Playwright MCP server. It is categorised as a Read tool in the Playwright MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_verify_list_visible? +

Register the Playwright MCP server in PolicyLayer and add a rule for browser_verify_list_visible: 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 Playwright. Nothing to install.

What risk level is browser_verify_list_visible? +

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

Can I rate-limit browser_verify_list_visible? +

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

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

browser_verify_list_visible is provided by the Playwright MCP server (hanato238/playwright-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Playwright, and thousands of servers like it.

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