delete_event

THE RISK

Critical Risk

Why delete_event needs a policy

Deleting a calendar event is a destructive action that cannot be undone—the event and its associated data are permanently removed. This falls squarely into the Destructive category. While the blast radius is limited to calendar data (not system-wide or financial), the irreversible nature and potential impact on scheduled activities (meetings, reminders, coordination) justifies a 'high' severity rating.

From the tool's definition Tool name: 'delete_event' and description 'Delete a calendar event.' The verb 'Delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_event gives an agent:

POLICY

How to control delete_event

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_event"
  ]
}

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

Create a free account and register Freshdesk — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Freshdesk tools

Financial create_quickbooks_bill Create a new bill (accounts payable) in QuickBooks Online. Example: { Financial create_quickbooks_invoice Create a new invoice in QuickBooks Online. Example: { Destructive cancel_runway_task Cancel a pending/running task or delete a completed task. Saves credits if cancelled befor Destructive delete_custom_voice Delete a custom voice by ID. This is permanent and cannot be undone. Destructive delete_email Delete or move an email to trash. Destructive delete_file Delete a file or folder from OneDrive. Destructive delete_library_item Delete a file or folder from a SharePoint document library. Destructive delete_list_item Delete an item from a SharePoint list.

All 422 Freshdesk tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Freshdesk → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_event

What does the delete_event tool do? +

Delete a calendar event. It is categorised as a Destructive tool in the Freshdesk 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 delete_event? +

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

What risk level is delete_event? +

delete_event 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 delete_event? +

Yes. Add a rate_limit block to the delete_event 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 delete_event completely? +

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

delete_event is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Freshdesk tool call.

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

CHECK YOUR STACK →