update_notification_schedule

Update an existing notification schedule

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

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/update-notification-schedule.md

WHAT IT DOES

What update_notification_schedule does on Unofficial FortiMonitor MCP Server

AI agents use update_notification_schedule to create or update resources in Unofficial FortiMonitor MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unofficial FortiMonitor MCP Server environment.

RISK

Why update_notification_schedule is rated Medium

This tool modifies an existing notification schedule configuration, which is a reversible operation (the schedule can be updated again or reverted). It does not execute external actions, delete data irreversibly, or involve financial transactions.

From the tool's definition Tool name 'update_notification_schedule' and description 'Update an existing notification schedule' indicate modification of configuration data. The verb 'update' is characteristic of Write operations that create or modify data reversibly.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_notification_schedule, this is the rule to start with:

update_notification_schedule Rate-limited

update_notification_schedule stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_notification_schedule": {
      "limits": [
        {
          "counter": "update_notification_schedule_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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 update_notification_schedule call is checked against it from then on.

FAQ

Questions about update_notification_schedule

What does the update_notification_schedule tool do? +

Update an existing notification schedule. It is categorised as a Write tool in the Unofficial FortiMonitor MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_notification_schedule? +

Register the Unofficial FortiMonitor MCP Server MCP server in PolicyLayer and add a rule for update_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 update_notification_schedule? +

update_notification_schedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_notification_schedule? +

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

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

update_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 →

Across the catalogue

sms_schedule on Twilio SMS MCP Server →aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →