delete_server

Delete a monitored server from FortiMonitor.

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-server.md

What delete_server does on Unofficial FortiMonitor MCP Server

AI agents call delete_server 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_server is rated Critical

Deletion of a monitored server is a destructive action that cannot be undone. The server record and associated monitoring data are permanently removed from the system. This has a significant blast radius if triggered by an AI agent without proper authorization or context, as it would disable monitoring for a critical infrastructure component.

From the tool's definition Tool name is 'delete_server' and description states 'Delete a monitored server from FortiMonitor' — the verb 'delete' indicates irreversible removal of a resource.

Questions about delete_server

What does the delete_server tool do? +

Delete a monitored server from FortiMonitor. 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_server? +

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

delete_server 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_server? +

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

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

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