delete_rule
Requests deletion of an existing GigaMail reply rule; a human must approve the request at the PC, and the rule cannot be restored (pause it to stop temporarily).
Instructions
Ask for a reply rule to be deleted. A reply rule tells GigaMail that, for mail from the given senders (or arriving in the given folder), it prepares a reply from the listed documents, in the given style, within a daily cap and a cooldown per sender, until the rule expires. In semi mode it prepares each reply and waits for the user's approval; in auto mode it replies without asking, so an auto rule is a standing permission to send mail. TWO-PHASE, HUMAN-APPROVED: the first call (no request_id) executes nothing — it returns status=approval_required with a preview of exactly what would happen and a request_id. A human approves out of band, only at the PC (GigaMail console or CLI, never Telegram); the second call with that request_id executes the payload that was approved (the approved arguments, not the ones passed the second time). Requests expire (default 15 min); identical pending requests are deduplicated; more than 20 requests/hour per tool are refused (status=rate_limited). Every phase is written to the audit log. The rule's history of handled mails goes with it, and a deleted rule cannot be brought back: to stop a rule for a while use pause_rule instead. The preview shows the whole rule being deleted. The request is approved only by the user at the PC, with a click on the confirmation (never from Telegram or by you). You cannot approve it: show the preview and ask the user to approve it in the GigaMail console, then call again with the request_id. Returns {success, rule_id, state: 'deleted'}.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"rule_id": "<rule_id>"
},
"name": "delete_rule"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| rule_id | Yes | Rule id exactly as returned by list_rules (for example 'rule_1a2b3c4d'). | |
| request_id | No | Omit on the first call. On the first call the tool does NOT execute: it returns status=approval_required, a preview and a request_id. A human must approve that request_id at the PC (GigaMail console or `gigamail approvals approve`, never Telegram). Then call again with the same request_id to execute. The agent cannot approve; repeating the call without approval just returns awaiting_approval. |