update_account
Update CRM account/customer profile fields such as name, phone, email, life stage, owner, notes, or member code.
This record as markdown: /tools/io-favcrm-favcrm/update-account.md
What update_account does on FavCRM
AI agents use update_account 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 | — | Account/customer display name |
type | string | — | Account type |
email | string | — | Email address |
notes | string | — | Internal notes |
phone | string | — | Phone number |
gender | string | — | Gender |
source | string | — | Acquisition source |
lastName | object | — | Last name for individual accounts |
accountId | string | Yes | The account ID to update |
firstName | object | — | First name for individual accounts |
lifeStage | string | — | CRM life stage |
assignedTo | object | — | Assigned team member user ID, or null to clear |
Parameters from the server's own tool schema.
Why update_account is rated Medium
This tool creates or modifies customer data reversibly without deleting information or executing external operations. While it handles sensitive customer information (name, phone, email), the modifications are not financial transactions, destructive deletions, or code execution.
From the tool's definition Tool performs data modification: 'Update CRM account/customer profile fields such as name, phone, email, life stage, owner, notes, or member code.' These are reversible changes to customer records.
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
The rule that runs update_account 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_account, this is the rule to start with:
update_account 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_account call is checked against it from then on.
Questions about update_account
Update CRM account/customer profile fields such as name, phone, email, life stage, owner, notes, or member code. 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_account accepts 12 parameters: name, type, email, notes, phone, gender, source, lastName, accountId, firstName, lifeStage, assignedTo. Required: accountId. 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_account: 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_account 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_account 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_account. 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_account 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