neuron_send_contact_card
Send a vCard contact card via WhatsApp with name, phone, and optional organization.
This record as markdown: /tools/io-github-conquext-neuron/neuron-send-contact-card.md
What neuron_send_contact_card does on Neuron
AI agents use neuron_send_contact_card to create or update resources in Neuron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neuron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | Recipient JID or phone number |
channelId | string | Yes | WhatsApp channel identifier (UUID) |
contactOrg | string | — | Organization or company name |
contactName | string | Yes | Full name of the contact to share |
contactPhone | string | Yes | Phone number in international format (e.g. '+2348012345678') |
Parameters from the server's own tool schema.
Why neuron_send_contact_card is rated Medium
This tool sends (creates and transmits) a vCard contact card message through WhatsApp. It modifies the messaging state by adding a new message to a conversation, which is reversible (messages can be deleted). This qualifies as Write rather than Execute because it performs a specific, bounded action (sending a formatted card) rather than arbitrary code execution.
From the tool's definition Tool name 'neuron_send_contact_card' and description 'Send a vCard contact card via WhatsApp with name, phone, and optional organization' indicates creation/transmission of a contact card message.
Attacks that exploit this kind of access
The rule that runs neuron_send_contact_card safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Neuron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For neuron_send_contact_card, this is the rule to start with:
neuron_send_contact_card 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 Neuron, apply this rule, and every neuron_send_contact_card call is checked against it from then on.
Questions about neuron_send_contact_card
Send a vCard contact card via WhatsApp with name, phone, and optional organization. It is categorised as a Write tool in the Neuron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
neuron_send_contact_card accepts 5 parameters: to, channelId, contactOrg, contactName, contactPhone. Required: to, channelId, contactName, contactPhone. The full parameter table on this page comes from the server's own tool schema.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_send_contact_card: 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 Neuron. Nothing to install.
neuron_send_contact_card 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 neuron_send_contact_card 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 neuron_send_contact_card. 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.
neuron_send_contact_card is provided by the Neuron MCP server (neuron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Neuron, and thousands of servers like it.
This server
Across the catalogue