Connect Playwright to Cursor
Give Cursor governed access to Playwright’s 27 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Playwright to Cursor in four steps
Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.
- 1
Approve Playwright in Runlayer
Add Playwright from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Cursor to Runlayer
Install the Runlayer CLI so Cursor can reach Playwright, which runs on the user’s machine. Auto Sync can then write Playwright into Cursor on macOS, Windows, and Linux.
Cursor setup guide - 3
Sign in to Playwright
Sign in the way Playwright requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Playwright from Cursor
Playwright’s approved tools appear in Cursor. Every call is checked against policy and recorded.
Tools
27 Playwright tools in Cursor
Runlayer policy decides which of these Cursor users can call.
Browser click
Perform click on a web page
Browser close
Close the page
Browser console messages
Returns all console messages
Browser drag
Perform drag and drop between two elements
Browser drop
Drop files or MIME-typed data onto an element, as if dragged from outside the page.
Browser emulate media
Emulate CSS media features for the page, for example switch between the light and dark color scheme.
Browser evaluate
Evaluate JavaScript expression on page or element
Browser file upload
Upload one or multiple files
Control
What Runlayer can see and stop in Cursor
Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.
Gateway policy (available)
Every Playwright call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Cursor as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Cursor runs it, including calls to MCP servers.
Block output after it runs (available)
Runlayer can block a tool’s output before Cursor’s model sees it.
Redact output in place (not available)
Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
In Cursor
- Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
- The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.
Frequently asked questions
Connect more