list_contacts
List contacts (people linked to CRM accounts), optionally filtered by account or search.
This record as markdown: /tools/io-favcrm-favcrm/list-contacts.md
What list_contacts does on FavCRM
AI agents call list_contacts to retrieve information from FavCRM without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max results (default 20) |
search | string | — | Match name, email, or phone |
accountId | string | — | Filter by account |
Parameters from the server's own tool schema.
Why list_contacts is rated Low
This tool retrieves and queries contact data from the CRM system without creating, modifying, deleting, or executing any operations. It is a standard data retrieval function typical of Read operations. The blast radius of misuse is minimal—an agent could retrieve contact information but cannot alter it or trigger further actions.
From the tool's definition Tool name is 'list_contacts' and description states it 'List contacts...optionally filtered by account or search.' The verb 'list' and the filtering operations are read-only query operations with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_contacts 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 list_contacts, this is the rule to start with:
list_contacts is read-only, so it stays allowed. 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 list_contacts call is checked against it from then on.
Questions about list_contacts
List contacts (people linked to CRM accounts), optionally filtered by account or search. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
list_contacts accepts 3 parameters: limit, search, 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 list_contacts: 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.
list_contacts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_contacts 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 list_contacts. 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.
list_contacts 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