This record as markdown: /tools/io-github-dave-london-npm/playwright.md
What playwright does on Npm
AI agents invoke playwright to trigger actions in Npm. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why playwright is rated High
Playwright tests execute browser automation scripts that can interact with external systems, websites, and services. The tool actively runs code/scripts in a browser context, making it Execute category. Misuse could trigger unintended browser actions, form submissions, or interactions with live systems, giving it high severity.
From the tool's definition Runs Playwright tests with JSON reporter and returns structured results with pass/fail status, duration, and error messages.
Attacks that exploit this kind of access
The rule that runs playwright safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Npm, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For playwright, this is the rule to start with:
playwright stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Npm, apply this rule, and every playwright call is checked against it from then on.
Questions about playwright
Runs Playwright tests with JSON reporter and returns structured results with pass/fail status, duration, and error messages. It is categorised as a Execute tool in the Npm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Npm MCP server in PolicyLayer and add a rule for playwright: 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 Npm. Nothing to install.
playwright is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the playwright 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 playwright. 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.
playwright is provided by the Npm MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Npm, and thousands of servers like it.
This server
Across the catalogue