playwright-mcp-server

The server uses `helmet` for basic security headers and `cors` (all origins allowed, which might be overly permissive for some use cases). It explicitly mentions non-root container execution and resource limits in Docker Compose, which are good practices. There's no use of `eval` or direct `child_process` execution. However, user-provided `url` and `selector` parameters are passed directly to Playwright methods. While Playwright's APIs generally handle this safely, a malicious or overly complex selector could potentially be exploited for resource exhaustion or unexpected behavior, despite the README's claim of 'Input validation' which isn't explicitly visible in the `server.js` snippet beyond basic existence checks.