browser_verify_text_visible
AI agents call browser_verify_text_visible to retrieve information from Playwright MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool checks or asserts whether text is visible on a page, which is a read-only query operation. It retrieves information about the page state (text visibility) with no side effects. The verb 'verify' indicates assertion/validation rather than action.
From the tool's definition Tool name 'browser_verify_text_visible' and context as browser automation tool that verifies/checks visibility of text elements without modifying state.
Attacks that exploit this kind of access
browser_verify_text_visible. It is categorised as a Read tool in the Playwright MCP MCP Server, which means it retrieves data without modifying state.
Register the Playwright MCP server in PolicyLayer and add a rule for browser_verify_text_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 MCP. Nothing to install.
browser_verify_text_visible 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 browser_verify_text_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.
Set action: deny in the PolicyLayer policy for browser_verify_text_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.
browser_verify_text_visible is provided by the Playwright MCP server (lysander72/playwright-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 →