AI agents call search_contacts to retrieve information from Twenty 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 read-only search query against the CRM database. It retrieves contact records matching search criteria but produces no side effects, reversible changes, or irreversible deletions. The blast radius of misuse is minimal—worst case is exposure of contact information already in the system. No financial transactions, code execution, or data destruction can occur through this tool alone.
From the tool's definition Tool name 'search_contacts' and description 'Search for contacts in Twenty CRM' indicate a query operation that retrieves data without modifying it.
Documented attack patterns abuse exactly the kind of access search_contacts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Twenty MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_contacts:
{
"version": "1",
"default": "deny",
"tools": {
"search_contacts": {}
}
}search_contacts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for contacts in Twenty CRM. It is categorised as a Read tool in the Twenty MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Twenty MCP Server MCP server in PolicyLayer and add a rule for 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 Twenty MCP Server. Nothing to install.
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 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 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.
search_contacts is provided by the Twenty MCP Server MCP server (jezweb/twenty-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Twenty MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Twenty MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.