Probe a live web page in headless Chromium and return a structured map of
AI agents invoke analyze_url to trigger actions in Mk Qa Master. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool launches a headless Chromium browser to actively probe a live web page, which constitutes executing an external browser process and performing network requests. This goes beyond passive data retrieval — it triggers real browser operations whose effects depend on the target URL (e.g., JavaScript execution, cookies, session interactions).
From the tool's definition Probe a live web page in headless Chromium
Documented attack patterns abuse exactly the kind of access analyze_url gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mk Qa Master, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_url:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_url": {
"limits": [
{
"counter": "analyze_url_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}analyze_url stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Probe a live web page in headless Chromium and return a structured map of. It is categorised as a Execute tool in the Mk Qa Master MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mk Qa Master MCP server in PolicyLayer and add a rule for analyze_url: 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 Mk Qa Master. Nothing to install.
analyze_url is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the analyze_url 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_url. 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_url is provided by the Mk Qa Master MCP server (kao273183/mk-qa-master). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mk Qa Master, 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.
22 Mk Qa Master tools catalogued and risk-classified — across an index of 43,000+ MCP servers.