This record as markdown: /tools/alexgladkov-claude-in-mobile/visual-list.md
What visual_list does on Claude Mobile
AI agents call visual_list to retrieve information from Claude Mobile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why visual_list is rated Low
The tool retrieves or queries a collection of saved visual baselines for comparison purposes (likely used in UI testing workflows). This is a read-only operation that has no side effects, does not execute code or commands, and does not modify any state. The blast radius of misuse is minimal — an attacker could only discover what visual baselines exist in the system, not alter them or trigger actions.
From the tool's definition Tool name is 'visual_list' and description states 'List saved visual baselines' — a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs visual_list 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_list, this is the rule to start with:
visual_list is read-only, so it stays allowed. 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_list call is checked against it from then on.
Questions about visual_list
List saved visual baselines. It is categorised as a Read tool in the Claude Mobile MCP Server, which means it retrieves data without modifying state.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for visual_list: 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_list 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 visual_list 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_list. 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_list 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.
This server
Across the catalogue