delete_rotating_contact

Delete a rotating contact schedule.

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-rotating-contact.md

What delete_rotating_contact does on Unofficial FortiMonitor MCP Server

AI agents call delete_rotating_contact 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.

Why delete_rotating_contact is rated Critical

The tool performs an irreversible deletion of a contact schedule. While not as critical as deleting servers or alerts, rotating contact schedules are part of the notification infrastructure, and their deletion cannot be undone without manual reconfiguration. This fits the Destructive category (delete operations).

From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a rotating contact schedule' — this is an irreversible deletion operation that destroys configuration data.

Questions about delete_rotating_contact

What does the delete_rotating_contact tool do? +

Delete a rotating contact schedule. 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_rotating_contact? +

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

delete_rotating_contact 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_rotating_contact? +

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

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

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