AI agents invoke long_press to trigger actions in Phantom. 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.
A long press is a UI interaction that triggers external operations on a simulator/emulator or real device. It falls under Execute as it performs a browser/device action whose effects depend on which element is targeted. The description is truncated ('Appui long sur un élément de l') reducing confidence slightly, but the tool name and context make the action clear.
From the tool's definition 'long_press' - performs a long press action on a UI element, which is a touch/interaction automation action on a device
Attacks that exploit this kind of access
Appui long sur un élément de l. It is categorised as a Execute tool in the Phantom MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Phantom MCP server in PolicyLayer and add a rule for long_press: 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.
long_press 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 long_press 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 long_press. 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.
long_press 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 →