AI agents call list_devices to retrieve information from Phantom without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about connected iOS simulators, Android emulators, and real devices. It performs no side effects, creates no data, executes no code on devices, and deletes nothing. It is purely informational/interrogative in nature, fitting the Read category. Severity is low because misuse poses minimal risk—an agent listing devices cannot harm the system or data.
From the tool's definition Tool name is 'list_devices' and description states it 'Liste tous les devices disponibles' (lists all available devices). The verb 'liste' (list) and the action of displaying available devices without modification indicates a read-only query operation.
Attacks that exploit this kind of access
Liste tous les devices disponibles — simulateurs iOS, émulateurs Android, et vrais devices connectés. Affiche la plateforme et l. It is categorised as a Read tool in the Phantom MCP Server, which means it retrieves data without modifying state.
Register the Phantom MCP server in PolicyLayer and add a rule for list_devices: 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 Phantom. Nothing to install.
list_devices 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 list_devices 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 list_devices. 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.
list_devices is provided by the Phantom MCP server (nthimpulse/phantom-mcp). 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 →