<use_case> Deletes rows from the specified table based on the given criteria. </use_case>
AI agents call delete_rows to permanently remove resources in Zoho Analytics — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
orgId | string | — | The organization ID for the request, if applicable. This is a mandatory parameter for shared workspaces |
tableId | string | Yes | The ID of the table from which rows will be deleted |
criteria | string | Yes | A string representing the criteria for selecting rows to delete. Example criteria: "\"SalesTable\".\"Region\"='East'" |
workspaceId | string | Yes | The ID of the workspace where the table is located |
Parameters from the server's own tool schema.
This tool permanently removes data from a table without the ability to undo the operation. While not as severe as dropping an entire table, deleting rows is a destructive action that results in data loss.
From the tool's definition Tool name is 'delete_rows' and description states it 'Deletes rows from the specified table based on the given criteria.' Deletion of data rows is irreversible.
Attacks that exploit this kind of access
<use_case> Deletes rows from the specified table based on the given criteria. </use_case>. It is categorised as a Destructive tool in the Zoho Analytics MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_rows accepts 4 parameters: orgId, tableId, criteria, workspaceId. Required: tableId, criteria, workspaceId. The full parameter table on this page comes from the server's own tool schema.
Register the Zoho Analytics MCP server in PolicyLayer and add a rule for delete_rows: 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 Analytics. Nothing to install.
delete_rows 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_rows 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_rows. 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_rows is provided by the Zoho Analytics MCP server (zoho-analytics-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 →