delete_ips_sensor

A destructive tool on the Fortimanager MCP server.

SERVERFortimanager SOURCEjmpijll/fortimanager-mcp
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/jmpijll-fortimanager-mcp/delete-ips-sensor.md

What delete_ips_sensor does on Fortimanager

AI agents call delete_ips_sensor to permanently remove resources in Fortimanager, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_ips_sensor is rated Critical

The delete prefix unambiguously indicates irreversible data deletion. IPS sensors are security infrastructure components; deleting one removes protection rules and cannot be easily undone. While the description is empty (reducing confidence slightly), the name alone provides sufficient evidence. This is Destructive rather than Write because deletion is non-reversible and impacts critical security infrastructure.

From the tool's definition Tool name is 'delete_ips_sensor' which uses 'delete' verb, indicating irreversible removal of an IPS (Intrusion Prevention System) sensor configuration.

Questions about delete_ips_sensor

What does the delete_ips_sensor tool do? +

delete_ips_sensor is a destructive tool on the Fortimanager MCP server. It is categorised as a Destructive tool in the Fortimanager 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_ips_sensor? +

Register the Fortimanager MCP server in PolicyLayer and add a rule for delete_ips_sensor: 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. Nothing to install.

What risk level is delete_ips_sensor? +

delete_ips_sensor 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_ips_sensor? +

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

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

delete_ips_sensor is provided by the Fortimanager MCP server (jmpijll/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Fortimanager, 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 Fortimanager'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.