sendgrid_add_contact
Add or update a marketing contact in SendGrid.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/sendgrid-add-contact.md
What sendgrid_add_contact does on UnClick
AI agents use sendgrid_add_contact to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | Contact email address |
api_key | string | Yes | SendGrid API key |
list_ids | array | — | List IDs to add the contact to |
last_name | string | — | Last name |
first_name | string | — | First name |
phone_number | string | — | Phone number |
Parameters from the server's own tool schema.
Why sendgrid_add_contact is rated Medium
This tool creates new contacts or modifies existing contact records in SendGrid, a third-party email marketing platform. It is reversible (contacts can be deleted or modified later), so it falls under Write rather than Destructive.
From the tool's definition Tool description: 'Add or update a marketing contact in SendGrid.' The verbs 'add' and 'update' indicate creation and modification of data.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs sendgrid_add_contact safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sendgrid_add_contact, this is the rule to start with:
sendgrid_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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every sendgrid_add_contact call is checked against it from then on.
Questions about sendgrid_add_contact
Add or update a marketing contact in SendGrid. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
sendgrid_add_contact accepts 6 parameters: email, api_key, list_ids, last_name, first_name, phone_number. Required: email, api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for sendgrid_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 UnClick. Nothing to install.
sendgrid_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 sendgrid_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 sendgrid_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.
sendgrid_add_contact is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue