AI agents invoke find_phone to trigger actions in PhonePi MCP. 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.
This tool triggers an external operation on a physical device (causing it to emit a sound/beep). It doesn't read data, write/modify stored data, delete anything, or move money — it executes a remote device action. The blast radius is minimal since the only effect is an audible beep on a phone.
From the tool's definition Make the phone beep to help locate it
Documented attack patterns abuse exactly the kind of access find_phone gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PhonePi MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for find_phone:
{
"version": "1",
"default": "deny",
"tools": {
"find_phone": {
"limits": [
{
"counter": "find_phone_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}find_phone 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.
Free to start. No card required.
Make the phone beep to help locate it. It is categorised as a Execute tool in the PhonePi MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PhonePi MCP server in PolicyLayer and add a rule for find_phone: 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 PhonePi MCP. Nothing to install.
find_phone 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 find_phone 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 find_phone. 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.
find_phone is provided by the PhonePi MCP server (priyankark/phonepi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 PhonePi MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
22 PhonePi MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.