Collect all visible, unique locators from the current page and generate a Page Object Model (POM) file. Automatically identifies the best locator strategy for each element (data-test attributes, role-based, ID, CSS). Use this when you need to create page objects or collect element selectors.
AI agents call playwright_collect_locators to retrieve information from RunAutomation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads/inspects the current page to collect element locators and generates a POM file. It does not modify page state, execute user code, or perform destructive actions. The file generation is a local artifact creation (Write-like), but the primary operation is reading/analyzing the DOM, and generating a POM file is a low-risk side effect used for test development purposes.
From the tool's definition Collect all visible, unique locators from the current page and generate a Page Object Model (POM) file. Automatically identifies the best locator strategy for each element
Documented attack patterns abuse exactly the kind of access playwright_collect_locators gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RunAutomation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for playwright_collect_locators:
{
"version": "1",
"default": "deny",
"tools": {
"playwright_collect_locators": {}
}
}playwright_collect_locators is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Collect all visible, unique locators from the current page and generate a Page Object Model (POM) file. Automatically identifies the best locator strategy for each element (data-test attributes, role-based, ID, CSS). Use this when you need to create page objects or collect element selectors. It is categorised as a Read tool in the RunAutomation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RunAutomation MCP Server MCP server in PolicyLayer and add a rule for playwright_collect_locators: 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 RunAutomation MCP Server. Nothing to install.
playwright_collect_locators 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 playwright_collect_locators 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_collect_locators. 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_collect_locators is provided by the RunAutomation MCP Server MCP server (tayyabakmal1/runautomation-mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RunAutomation MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
91 RunAutomation MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.