Connect Playwright to ECA
Give ECA governed access to Playwright’s 27 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Playwright to ECA in four steps
Admins approve the server once. Everyone in ECA 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 ECA to Runlayer
Install the Runlayer CLI so ECA can reach Playwright, which runs on the user’s machine.
ECA 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 ECA
Playwright’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
27 Playwright tools in ECA
Runlayer policy decides which of these ECA 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 ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every Playwright call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more