Analyzes a WebDriverIO test file using AST parsing and extracts detailed information about its structure, selectors, commands, and dependencies. Detects if test is already partially migrated to Playwright.
AI agents call analyze_wdio_test to retrieve information from MCP Server - Test Migration (WDIO to Playwright) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static code analysis—parsing and inspection of test files to extract structure, selectors, commands, and dependencies. It reads source code, identifies patterns, and reports findings. No data is created, modified, deleted, or executed. The action is purely informational with no side effects, fitting the Read category definition of querying/retrieving data without modification.
From the tool's definition Tool 'analyzes' and 'extracts detailed information' about test files, performing static AST parsing without modifying files or executing tests. No side effects mentioned.
Attacks that exploit this kind of access
Analyzes a WebDriverIO test file using AST parsing and extracts detailed information about its structure, selectors, commands, and dependencies. Detects if test is already partially migrated to Playwright. It is categorised as a Read tool in the MCP Server - Test Migration (WDIO to Playwright) MCP Server, which means it retrieves data without modifying state.
Register the MCP Server - Test Migration (WDIO to Playwright) MCP server in PolicyLayer and add a rule for analyze_wdio_test: 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 MCP Server - Test Migration (WDIO to Playwright). Nothing to install.
analyze_wdio_test 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 analyze_wdio_test 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 analyze_wdio_test. 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.
analyze_wdio_test is provided by the MCP Server - Test Migration (WDIO to Playwright) MCP server (lucad87/mcp-server-tests-migration). 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 →