Critical Risk →

reminders.delete_reminder

Delete a reminder.

How to control reminders.delete_reminder ↓

What reminders.delete_reminder does on Orchard

AI agents call reminders.delete_reminder to permanently remove resources in Orchard — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why reminders.delete_reminder needs a policy

Deletion operations are irreversible and cannot be undone. Even though a single reminder deletion has a limited scope (not a full account wipe), the destructive nature of delete operations and the fact that reminders may contain important task information or time-sensitive instructions justifies the Destructive category.

From the tool's definition Tool name is 'reminders.delete_reminder' with description 'Delete a reminder.' The verb 'delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access reminders.delete_reminder gives an agent:

How to control reminders.delete_reminder

PolicyLayer is an MCP gateway — it sits between your AI agents and Orchard, and nothing reaches the server without passing your rules. This is the rule we recommend for reminders.delete_reminder:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "reminders.delete_reminder"
  ]
}

reminders.delete_reminder disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Orchard — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about reminders.delete_reminder

What does the reminders.delete_reminder tool do? +

Delete a reminder. It is categorised as a Destructive tool in the Orchard MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on reminders.delete_reminder? +

Register the Orchard MCP server in PolicyLayer and add a rule for reminders.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 Orchard. Nothing to install.

What risk level is reminders.delete_reminder? +

reminders.delete_reminder is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit reminders.delete_reminder? +

Yes. Add a rate_limit block to the reminders.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.

How do I block reminders.delete_reminder completely? +

Set action: deny in the PolicyLayer policy for reminders.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.

What MCP server provides reminders.delete_reminder? +

reminders.delete_reminder is provided by the Orchard MCP server (l22-io/orchard-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Orchard tool call.

Start from Orchard, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

65 Orchard tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.