search_crm
Search across CRM accounts and contacts by name, email, or phone.
This record as markdown: /tools/io-favcrm-favcrm/search-crm.md
What search_crm does on FavCRM
AI agents call search_crm 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 per entity (default 10) |
query | string | Yes | Search string |
Parameters from the server's own tool schema.
Why search_crm is rated Low
This is a search/query operation that retrieves data from the CRM without altering it. It falls clearly into the Read category. Severity is medium rather than low because CRM systems typically contain sensitive customer contact information (names, emails, phone numbers), and unrestricted search access could enable reconnaissance, social engineering, or privacy violations.
From the tool's definition Tool description states it 'Search[es] across CRM accounts and contacts by name, email, or phone' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs search_crm 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 search_crm, this is the rule to start with:
search_crm 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 search_crm call is checked against it from then on.
Questions about search_crm
Search across CRM accounts and contacts by name, email, or phone. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
search_crm accepts 2 parameters: limit, query. Required: query. 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 search_crm: 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.
search_crm 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 search_crm 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 search_crm. 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.
search_crm 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