Fetch the total number of records in the module, or fetch the number of records that match a criteria. Count filters can be custom view ID, criteria, email, phone number, or a word in the record. For a total count, set count_type=
AI agents call count-zoho-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 retrieves aggregate count data from Zoho CRM without modifying, deleting, or executing any operations. It is a pure read operation that queries existing data. The server is explicitly read-only, and counting records is a standard non-destructive query. Misuse would have minimal blast radius (exposure of count information only).
From the tool's definition Tool description states it 'Fetch[es] the total number of records' and 'number of records that match a criteria' — query operations only.
Attacks that exploit this kind of access
Fetch the total number of records in the module, or fetch the number of records that match a criteria. Count filters can be custom view ID, criteria, email, phone number, or a word in the record. For a total count, set count_type=. 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 count-zoho-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.
count-zoho-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 count-zoho-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 count-zoho-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.
count-zoho-records is provided by the Zoho CRM MCP Server MCP server (whiteside-daniel/zohocrm-mcpserver). 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 →