Delete a single record by id.
AI agents call delete_record to permanently remove resources in Zoho CRM MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of records cannot be undone and represents permanent data loss. In a CRM context, deleting customer, contact, or transaction records can have serious business consequences. This is the most severe category applicable, superseding Write or Execute. Confidence is high because the intent is unambiguous, though actual blast radius depends on access controls and what records exist in the system.
From the tool's definition Tool name is 'delete_record' and description states 'Delete a single record by id.' The verb 'Delete' combined with removal of a record by identifier indicates irreversible data loss.
Attacks that exploit this kind of access
Delete a single record by id. It is categorised as a Destructive tool in the Zoho CRM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zoho CRM MCP Server MCP server in PolicyLayer and add a rule for delete_record: 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.
delete_record is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_record 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 delete_record. 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.
delete_record 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 →