visual_suite
Run visual comparison for all baselines matching filters (batch regression check)
This record as markdown: /tools/alexgladkov-claude-in-mobile/visual-suite.md
What visual_suite does on Claude Mobile
AI agents invoke visual_suite to trigger actions in Claude Mobile. 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.
Why visual_suite is rated High
This tool triggers an external testing operation that executes code logic to compare visuals in batch mode. While not destructive or financial, it runs automated processes on mobile devices whose scope and impact depend on arguments (which baselines are selected). This fits Execute rather than Read because it actively runs/triggers operations rather than merely retrieving data.
From the tool's definition Tool performs 'run visual comparison for all baselines matching filters (batch regression check)' — this executes an automated operation (visual regression testing) across multiple targets with parameters, whose effects depend on the filter arguments provided.
Attacks that exploit this kind of access
The rule that runs visual_suite safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For visual_suite, this is the rule to start with:
visual_suite 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every visual_suite call is checked against it from then on.
Questions about visual_suite
Run visual comparison for all baselines matching filters (batch regression check). It is categorised as a Execute tool in the Claude Mobile MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for visual_suite: 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 Claude Mobile. Nothing to install.
visual_suite 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 visual_suite 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 visual_suite. 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.
visual_suite is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Mobile, and thousands of servers like it.
Across the catalogue