delete_service
AI agents call delete_service to permanently remove resources in FortiManager MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'delete_service' clearly indicates irreversible deletion of data. Although the description is empty (lowering confidence slightly), the tool name combined with the FortiManager context—a critical network management system—indicates this tool permanently removes service configurations that cannot be automatically recovered.
From the tool's definition Tool name is 'delete_service' which explicitly indicates a deletion operation. In the context of FortiManager, a service deletion operation removes configuration data irreversibly.
Attacks that exploit this kind of access
delete_service. It is categorised as a Destructive tool in the FortiManager MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for delete_service: 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 FortiManager MCP Server. Nothing to install.
delete_service is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_service 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 delete_service. 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.
delete_service is provided by the FortiManager MCP Server MCP server (rstierli/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →