This record as markdown: /tools/io-github-heznpc-iconnect/add-contact-email.md
What add_contact_email does on Iconnect
AI agents use add_contact_email to create or update resources in Iconnect, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iconnect environment.
Why add_contact_email is rated Medium
This tool creates or modifies contact information reversibly—a new email can be added, edited, or removed from a contact without permanent loss of other data. It falls squarely into the Write category.
From the tool's definition Tool name 'add_contact_email' and description 'Add an email address to an existing contact' indicate creation/modification of contact data in the Apple ecosystem.
Attacks that exploit this kind of access
The rule that runs add_contact_email safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_contact_email, this is the rule to start with:
add_contact_email 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every add_contact_email call is checked against it from then on.
Questions about add_contact_email
Add an email address to an existing contact. It is categorised as a Write tool in the Iconnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iconnect MCP server in PolicyLayer and add a rule for add_contact_email: 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 Iconnect. Nothing to install.
add_contact_email 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_email 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_email. 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_email is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue