Mobile 版的 analyze_url：透過 maestro hierarchy dump 當前 iOS Simulator /
AI agents call analyze_screen to retrieve information from Mk Qa Master without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and retrieves the current state of a mobile screen's view hierarchy without modifying, executing commands, or destructive actions. It is analogous to the sibling tool 'analyze_url' (Web DOM probe), both serving as passive inspection utilities for QA analysis. The severity is low because misuse would only expose screen structure information without enabling harmful actions.
From the tool's definition Tool name and description indicate 'analyze_screen' performs a mobile DOM probe via 'maestro hierarchy' dump to inspect current iOS Simulator / Android Emulator state; 'analyze' and 'dump' are read-only introspection operations with no side effects.
Documented attack patterns abuse exactly the kind of access analyze_screen 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_screen:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_screen": {}
}
}analyze_screen 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.
Mobile 版的 analyze_url：透過 maestro hierarchy dump 當前 iOS Simulator /. It is categorised as a Read tool in the Mk Qa Master MCP Server, which means it retrieves data without modifying state.
Register the Mk Qa Master MCP server in PolicyLayer and add a rule for analyze_screen: 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_screen 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_screen 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_screen. 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_screen 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.