crm_search_contacts
Substring search across name, email, phone, and title. Returns contacts ordered newest-updated first.
This record as markdown: /tools/com-getmunin-munin/crm-search-contacts.md
What crm_search_contacts does on Munin
AI agents call crm_search_contacts to retrieve information from Munin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crm_search_contacts is rated Low
This tool queries contact data and returns results ordered by update time. It performs a search operation (substring matching) across standard contact fields without creating, modifying, or deleting any data. This is a classic Read operation.
From the tool's definition Tool description states 'Substring search' and 'Returns contacts' — a retrieval operation with no modification or deletion. No side effects mentioned.
Attacks that exploit this kind of access
The rule that runs crm_search_contacts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crm_search_contacts, this is the rule to start with:
crm_search_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 Munin, apply this rule, and every crm_search_contacts call is checked against it from then on.
Questions about crm_search_contacts
Substring search across name, email, phone, and title. Returns contacts ordered newest-updated first. It is categorised as a Read tool in the Munin MCP Server, which means it retrieves data without modifying state.
Register the Munin 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 Munin. 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 Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Munin, and thousands of servers like it.
This server
Across the catalogue