drop_event

Drop a scheduled event.

SERVERMcp Windows SOURCEmukul975/mcp-windows-automation

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/mukul975-mcp-windows-automation/drop-event.md

WHAT IT DOES

What drop_event does on Mcp Windows

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

RISK

Why drop_event is rated Critical

The tool performs an irreversible deletion of a scheduled event. Once dropped, the event is removed and cannot be recovered through normal means. This falls under the Destructive category as it permanently removes system configuration/scheduling data.

From the tool's definition Tool name is 'drop_event' and description states 'Drop a scheduled event' - 'drop' is a clear destructive operation verb indicating irreversible deletion/removal of a scheduled event from the Windows system.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs drop_event safely

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

drop_event Hidden

drop_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": [
    "drop_event"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about drop_event

What does the drop_event tool do? +

Drop a scheduled event. It is categorised as a Destructive tool in the Mcp Windows 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 drop_event? +

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

What risk level is drop_event? +

drop_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 drop_event? +

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

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

drop_event is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Windows, and thousands of servers like it.

This server

All 441 Mcp Windows tools → Critical-risk tools on this server →

Across the catalogue

calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →