get_notification_schedule_servers

Get servers associated with a notification schedule.

SERVERUnofficial FortiMonitor MCP Server SOURCEgjenkins20/unofficial-fortimonitor-mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What get_notification_schedule_servers does on Unofficial FortiMonitor MCP Server

AI agents call get_notification_schedule_servers 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_servers is rated Low

This tool retrieves information about which servers are linked to a notification schedule. It performs a query operation that does not create, modify, delete, or execute any actions. The action is purely informational, making it a Read operation with low severity since unauthorized access to this metadata poses minimal risk compared to other categories.

From the tool's definition Tool name includes 'get_' verb and description states 'Get servers associated with a notification schedule' — indicates data retrieval with no modification or side effects.

Questions about get_notification_schedule_servers

What does the get_notification_schedule_servers tool do? +

Get servers associated with a 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.

How do I enforce a policy on get_notification_schedule_servers? +

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

get_notification_schedule_servers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_notification_schedule_servers? +

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

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

get_notification_schedule_servers 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Unofficial FortiMonitor MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.