delete_event

Permanently delete a calendar event. This action cannot be undone.

SERVERHuly SOURCE@firfi/huly-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-event.md

WHAT IT DOES

What delete_event does on Huly

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

RISK

Why delete_event is rated Critical

This tool permanently and irreversibly deletes data (a calendar event) with no undo capability. Destructive category is most appropriate as it cannot be reversed. Severity is high because an AI agent misusing this could delete important business calendar events, impacting scheduling and commitments, though the blast radius is typically limited to individual calendar entries rather than system-wide data.

From the tool's definition Tool name 'delete_event' combined with description stating 'Permanently delete a calendar event. This action cannot be undone.' explicitly indicates irreversible deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_event safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_event, this is the rule to start with:

delete_event Hidden

delete_event is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every delete_event call is checked against it from then on.

FAQ

Questions about delete_event

What does the delete_event tool do? +

Permanently delete a calendar event. This action cannot be undone. It is categorised as a Destructive tool in the Huly 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 Huly 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 Huly. 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 Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 518 Huly tools → Critical-risk tools on this server →

Across the catalogue

calendar_delete_event on Templonix Lite MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →