Search for contacts by name or email.
AI agents call crm_search_contacts to retrieve information from Medicus CRM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search operation to retrieve contact information, which is a read-only action. It queries existing data without creating, modifying, deleting, or executing any operations. The low severity reflects minimal blast radius if misused—an agent could retrieve contact information but cannot alter or delete records, move money, or trigger external operations.
From the tool's definition Tool name 'crm_search_contacts' and description 'Search for contacts by name or email' indicate query/retrieval operations with no side effects.
Attacks that exploit this kind of access
Search for contacts by name or email. It is categorised as a Read tool in the Medicus CRM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Medicus CRM MCP Server MCP server in PolicyLayer and add a rule for crm_search_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 Medicus CRM MCP Server. Nothing to install.
crm_search_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 crm_search_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 crm_search_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.
crm_search_contacts is provided by the Medicus CRM MCP Server MCP server (soundrolling/crmmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →