get_notification_schedule_details
Get detailed information about a specific notification schedule,
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/get-notification-schedule-details.md
What get_notification_schedule_details does on Unofficial FortiMonitor MCP Server
AI agents call get_notification_schedule_details 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_details is rated Low
This tool retrieves or queries details about an existing notification schedule with no side effects. It follows the standard Read pattern of fetching configuration or status information. The blast radius of misuse is minimal—an attacker could only gain visibility into notification schedule settings, not modify systems or trigger actions.
From the tool's definition Tool name 'get_notification_schedule_details' and description 'Get detailed information about a specific notification schedule' indicate a retrieval operation with the verb 'Get' and no mention of modification, deletion, or execution of operations.
Attacks that exploit this kind of access
The rule that runs get_notification_schedule_details 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_details, this is the rule to start with:
get_notification_schedule_details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Unofficial FortiMonitor MCP Server, apply this rule, and every get_notification_schedule_details call is checked against it from then on.
Questions about get_notification_schedule_details
Get detailed information about a specific notification schedule,. It is categorised as a Read tool in the Unofficial FortiMonitor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unofficial FortiMonitor MCP Server MCP server in PolicyLayer and add a rule for get_notification_schedule_details: 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.
get_notification_schedule_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_notification_schedule_details 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.
Set action: deny in the PolicyLayer policy for get_notification_schedule_details. 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.
get_notification_schedule_details 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.
More on Unofficial FortiMonitor MCP Server, and thousands of servers like it.
Across the catalogue