Crawl a webpage and extract all interactive elements like inputs, buttons and links with their locators. Always call this first before writing a test.
AI agents call crawl_page to retrieve information from QA Automation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool fetches and reads content from a webpage, extracting UI element metadata. It has no write or destructive side effects on the target system. Severity is medium because it initiates outbound network requests to arbitrary URLs, which could be misused for SSRF or unauthorized crawling of internal/external systems.
From the tool's definition Crawl a webpage and extract all interactive elements like inputs, buttons and links with their locators
Attacks that exploit this kind of access
Crawl a webpage and extract all interactive elements like inputs, buttons and links with their locators. Always call this first before writing a test. It is categorised as a Read tool in the QA Automation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QA Automation MCP Server MCP server in PolicyLayer and add a rule for crawl_page: 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 QA Automation MCP Server. Nothing to install.
crawl_page 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 crawl_page 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 crawl_page. 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.
crawl_page is provided by the QA Automation MCP Server MCP server (parajuliminiyan/playwrightmcp-server). 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 →