AI agents use send_notification to create or update resources in PhonePi MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PhonePi MCP environment.
This tool creates a new notification artifact on the phone (a reversible write operation). While notifications are intrusive user-facing actions, they do not modify persistent data, trigger financial transactions, execute arbitrary code, or destroy data. The impact is limited to displaying a message on the user's device.
From the tool's definition Tool name 'send_notification' and description 'Send a notification to the phone' indicate a write operation that creates a transient message on the device.
Documented attack patterns abuse exactly the kind of access send_notification 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 send_notification:
{
"version": "1",
"default": "deny",
"tools": {
"send_notification": {
"limits": [
{
"counter": "send_notification_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send_notification stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Send a notification to the phone. It is categorised as a Write tool in the PhonePi MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PhonePi MCP server in PolicyLayer and add a rule for send_notification: 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.
send_notification is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the send_notification 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 send_notification. 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.
send_notification 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.