set_primary_contact
Set a contact as the primary contact for its CRM account and demote other contacts on that account.
This record as markdown: /tools/io-favcrm-favcrm/set-primary-contact.md
What set_primary_contact does on FavCRM
AI agents use set_primary_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 |
|---|---|---|---|
contactId | string | Yes | The contact ID to make primary |
Parameters from the server's own tool schema.
Why set_primary_contact is rated Medium
This tool modifies data (contact primary status and demotion flags) but the changes are reversible — primary contact designations can be changed back, and demotions can be undone. No data is deleted, financial transactions occur, or destructive operations are performed.
From the tool's definition Tool description states it will 'Set a contact as the primary contact' and 'demote other contacts' — these are reversible modifications to contact metadata/roles within a CRM account.
Attacks that exploit this kind of access
The rule that runs set_primary_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 set_primary_contact, this is the rule to start with:
set_primary_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 set_primary_contact call is checked against it from then on.
Questions about set_primary_contact
Set a contact as the primary contact for its CRM account and demote other contacts on that 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.
set_primary_contact accepts 1 parameter: contactId. 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 set_primary_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.
set_primary_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 set_primary_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 set_primary_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.
set_primary_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