reminder_cancel
Cancel an active reminder by its trigger ID.
This record as markdown: /tools/io-github-saloprj-dialogbrain/reminder-cancel.md
What reminder_cancel does on Dialogbrain
AI agents call reminder_cancel to permanently remove resources in Dialogbrain, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | integer | — | Agent ID (required when calling from MCP; ignored in agentic mode). |
trigger_id | integer | Yes | ID of the reminder to cancel |
Parameters from the server's own tool schema.
Why reminder_cancel is rated Critical
Cancelling a reminder is an irreversible action — once cancelled, the scheduled reminder is permanently removed and will not fire. This matches the Destructive category (irreversibly deletes/overwrites a scheduled event). Severity is medium since the blast radius is limited to losing a scheduled reminder rather than data or financial impact.
From the tool's definition Cancel an active reminder by its trigger ID
Attacks that exploit this kind of access
The rule that runs reminder_cancel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reminder_cancel, this is the rule to start with:
reminder_cancel is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every reminder_cancel call is checked against it from then on.
Questions about reminder_cancel
Cancel an active reminder by its trigger ID. It is categorised as a Destructive tool in the Dialogbrain MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
reminder_cancel accepts 2 parameters: agent_id, trigger_id. Required: trigger_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for reminder_cancel: 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 Dialogbrain. Nothing to install.
reminder_cancel 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 reminder_cancel 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 reminder_cancel. 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.
reminder_cancel is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
Across the catalogue