list_records
AI agents call list_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.
The tool retrieves or queries data from Zoho CRM without side effects. No creation, modification, deletion, or execution capabilities are implied. It belongs in the Read category with low severity—misuse would only expose existing data, not alter or destroy it.
From the tool's definition Tool name 'list_records' and sibling context (get_record, get_module, list_modules, list_related_records, list_users) indicate data retrieval without modification. Description is empty, but naming convention and API pattern are unambiguous.
Attacks that exploit this kind of access
list_records. 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 list_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.
list_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 list_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 list_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.
list_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 →