delete_notification_schedule

Delete a notification schedule. Servers and contact groups using this

SERVERUnofficial FortiMonitor MCP Server SOURCEgjenkins20/unofficial-fortimonitor-mcp-server

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/gjenkins20-unofficial-fortimonitor-mcp-server/delete-notification-schedule.md

WHAT IT DOES

What delete_notification_schedule does on Unofficial FortiMonitor MCP Server

AI agents call delete_notification_schedule to permanently remove resources in Unofficial FortiMonitor MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_notification_schedule is rated Critical

This tool performs a destructive operation by deleting a notification schedule. Once deleted, the schedule cannot be recovered without manual recreation or backup restoration. The impact is irreversible, placing this firmly in the Destructive category rather than Write. Severity is high because deletion of notification schedules could disrupt alerting infrastructure, causing monitoring gaps and undetected incidents.

From the tool's definition Tool name is 'delete_notification_schedule' with description stating 'Delete a notification schedule.' The verb 'delete' indicates irreversible removal of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_notification_schedule safely

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

delete_notification_schedule Hidden

delete_notification_schedule 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_notification_schedule"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Unofficial FortiMonitor MCP Server, apply this rule, and every delete_notification_schedule call is checked against it from then on.

FAQ

Questions about delete_notification_schedule

What does the delete_notification_schedule tool do? +

Delete a notification schedule. Servers and contact groups using this. It is categorised as a Destructive tool in the Unofficial FortiMonitor MCP Server 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_notification_schedule? +

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

What risk level is delete_notification_schedule? +

delete_notification_schedule 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_notification_schedule? +

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

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

delete_notification_schedule is provided by the Unofficial FortiMonitor MCP Server MCP server (gjenkins20/unofficial-fortimonitor-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Unofficial FortiMonitor MCP Server, and thousands of servers like it.

This server

All 272 Unofficial FortiMonitor MCP Server tools → Critical-risk tools on this server →

Across the catalogue

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

Guides

Govern database agents →Blast radius →Tool call approval →