create_contact
Create a contact on an existing CRM account.
This record as markdown: /tools/io-favcrm-favcrm/create-contact.md
What create_contact does on FavCRM
AI agents use create_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 | Yes | Contact name |
email | string | — | |
phone | string | — | Phone |
jobTitle | string | — | Job title |
accountId | string | Yes | Owning account ID |
isPrimary | boolean | — | Mark as primary contact |
Parameters from the server's own tool schema.
Why create_contact is rated Medium
The tool creates new data (contacts) in the CRM system, which is a classic Write operation. It is not Read (no data retrieval), not Execute (no code execution or external triggers), not Destructive (the action is reversible—contacts can be deleted), and not Financial (no money movement).
From the tool's definition Tool name 'create_contact' and description 'Create a contact on an existing CRM account' indicate data creation. This is a reversible write operation that adds new customer/contact records to the CRM system.
Attacks that exploit this kind of access
The rule that runs create_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 create_contact, this is the rule to start with:
create_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 create_contact call is checked against it from then on.
Questions about create_contact
Create a contact on an existing CRM account. 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.
create_contact accepts 6 parameters: name, email, phone, jobTitle, accountId, isPrimary. Required: name, 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 create_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.
create_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 create_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 create_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.
create_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