get_notification_schedule_network_services

What get_notification_schedule_network_services does on Unofficial FortiMonitor MCP Server

AI agents call get_notification_schedule_network_services to retrieve information from Unofficial FortiMonitor MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_notification_schedule_network_services is rated Low

This tool retrieves configuration data about which monitoring checks are linked to a notification schedule. It performs a read-only query with no side effects, no code execution, no data modification, and no irreversible actions. The blast radius of misuse is minimal—an agent could only view existing notification schedule associations, not alter monitoring behavior or trigger actions.

From the tool's definition Tool name contains 'get' and description states 'Get network services (monitoring checks) associated with a notification schedule' - retrieves and queries data about notification schedules without modifying or executing operations.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_notification_schedule_network_services": {}
  }
}

Questions about get_notification_schedule_network_services