This record as markdown: /tools/com-quintadb-mcp/delete-reminder.md
What delete_reminder does on QuintaDB
AI agents call delete_reminder to permanently remove resources in QuintaDB, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
app_id | string | Yes | Project ID (from list_projects) |
reminder_id | string | Yes | Reminder ID (from list_reminders) |
Parameters from the server's own tool schema.
Why delete_reminder is rated Critical
The tool permanently removes a reminder record with no undo capability, matching the Destructive category definition. Severity is medium rather than high because reminders are typically low-criticality metadata; however, if reminders are tied to important workflows or compliance requirements in a business context, misuse could cause operational disruption.
From the tool's definition Tool name 'delete_reminder' combined with description 'Видалити нагадування' (Ukrainian for 'Delete reminder') indicates irreversible deletion of a reminder object.
Attacks that exploit this kind of access
The rule that runs delete_reminder safely
PolicyLayer is an MCP gateway: it sits between your AI agents and QuintaDB, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_reminder, this is the rule to start with:
delete_reminder 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 QuintaDB, apply this rule, and every delete_reminder call is checked against it from then on.
Questions about delete_reminder
Видалити нагадування. It is categorised as a Destructive tool in the QuintaDB MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_reminder accepts 2 parameters: app_id, reminder_id. Required: app_id, reminder_id. The full parameter table on this page comes from the server's own tool schema.
Register the QuintaDB MCP server in PolicyLayer and add a rule for delete_reminder: 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 QuintaDB. Nothing to install.
delete_reminder 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_reminder 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_reminder. 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_reminder is provided by the QuintaDB MCP server (https://quintadb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on QuintaDB, and thousands of servers like it.
Across the catalogue