This record as markdown: /tools/io-favcrm-favcrm/update-contact.md
What update_contact does on FavCRM
AI agents use update_contact to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Name |
email | string | — | Email address |
phone | string | — | Phone number |
jobTitle | string | — | Job title |
contactId | string | Yes | The contact ID |
isPrimary | boolean | — | Mark as the primary contact |
Parameters from the server's own tool schema.
Why update_contact is rated Medium
This tool modifies contact information in a CRM system. While not destructive (data remains recoverable), it creates reversible changes to customer records. In a CRM context, updating contacts can affect business operations and customer communications, warranting medium severity. The confidence is high because the intent is explicit from both name and description.
From the tool's definition Tool name is 'update_contact' and description states 'Update fields on an existing contact.' The verb 'update' indicates modification of existing data.
Attacks that exploit this kind of access
The rule that runs update_contact safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_contact, this is the rule to start with:
update_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 FavCRM, apply this rule, and every update_contact call is checked against it from then on.
Questions about update_contact
Update fields on an existing contact. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_contact accepts 6 parameters: name, email, phone, jobTitle, contactId, isPrimary. Required: contactId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for update_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 FavCRM. Nothing to install.
update_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 update_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 update_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.
update_contact is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue