Search records by criteria, email, phone, or word.
AI agents call search_records to retrieve information from Zoho 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 searches and queries on existing records in Zoho CRM without creating, modifying, deleting, or executing arbitrary operations. It retrieves data based on specified search parameters. The absence of any write, delete, or execute keywords, combined with the explicit 'search' function, clearly categorizes this as a Read operation.
From the tool's definition Tool name 'search_records' and description 'Search records by criteria, email, phone, or word' indicate retrieval/query operations with no modification or deletion of data.
Attacks that exploit this kind of access
Search records by criteria, email, phone, or word. It is categorised as a Read tool in the Zoho CRM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zoho CRM MCP Server MCP server in PolicyLayer and add a rule for search_records: 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 Zoho CRM MCP Server. Nothing to install.
search_records 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_records 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_records. 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_records is provided by the Zoho CRM MCP Server MCP server (lokimcpuniverse/zoho-crm-mcp-server). 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 →