检查 Playwright 浏览器驱动安装状态
AI agents call check_playwright_installation to retrieve information from YST KPI Daily Report Collector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a diagnostic/inspection tool that queries the system state of Playwright installation. It retrieves information about whether a dependency is installed but performs no modifications, executions of external systems, or destructive actions. It fits squarely in the Read category as a status-checking operation.
From the tool's definition Tool name 'check_playwright_installation' and description indicate it only checks/verifies the installation status of Playwright browser driver - a read-only diagnostic operation with no side effects or data modification.
Attacks that exploit this kind of access
检查 Playwright 浏览器驱动安装状态. It is categorised as a Read tool in the YST KPI Daily Report Collector MCP Server, which means it retrieves data without modifying state.
Register the YST KPI Daily Report Collector MCP server in PolicyLayer and add a rule for check_playwright_installation: 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 YST KPI Daily Report Collector. Nothing to install.
check_playwright_installation 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 check_playwright_installation 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 check_playwright_installation. 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.
check_playwright_installation is provided by the YST KPI Daily Report Collector MCP server (xuzan9396/yst_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 →