AI agents use add_contact 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 new contact entries, which is reversible (contacts can be deleted) but represents a write operation that modifies user data. Severity is medium because unauthorized contact addition could facilitate spam, phishing, or social engineering attacks, but the impact is limited compared to financial transactions or destructive operations.
From the tool's definition Tool name 'add_contact' and description 'Add a new contact to the phone' indicate creation of contact records, which is a write operation that modifies the device's contact database.
Documented attack patterns abuse exactly the kind of access add_contact 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 add_contact:
{
"version": "1",
"default": "deny",
"tools": {
"add_contact": {
"limits": [
{
"counter": "add_contact_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_contact 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.
Add a new contact 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 add_contact: 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.
add_contact 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 add_contact 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 add_contact. 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.
add_contact 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.