Critical Risk →

ips_sensor_delete

ips_sensor_delete

How to control ips_sensor_delete ↓

What ips_sensor_delete does on FortiOS 7 6 X MCP Server

AI agents call ips_sensor_delete to permanently remove resources in FortiOS 7 6 X MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why ips_sensor_delete needs a policy

IPS sensor deletion is an irreversible operation that removes security infrastructure configurations. In a FortiOS firewall context, deleting sensors disables intrusion prevention capabilities and cannot be undone without manual reconfiguration. The 'delete' action combined with 'sensor' (a named security policy object) places this firmly in the Destructive category.

From the tool's definition Tool name 'ips_sensor_delete' explicitly indicates deletion of IPS (Intrusion Prevention System) sensor configurations, which are security policies that cannot be trivially recreated.

Documented attack patterns abuse exactly the kind of access ips_sensor_delete gives an agent:

How to control ips_sensor_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and FortiOS 7 6 X MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ips_sensor_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "ips_sensor_delete"
  ]
}

ips_sensor_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register FortiOS 7 6 X MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about ips_sensor_delete

What does the ips_sensor_delete tool do? +

ips_sensor_delete. It is categorised as a Destructive tool in the FortiOS 7 6 X 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 ips_sensor_delete? +

Register the FortiOS 7 6 X MCP Server MCP server in PolicyLayer and add a rule for ips_sensor_delete: 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 FortiOS 7 6 X MCP Server. Nothing to install.

What risk level is ips_sensor_delete? +

ips_sensor_delete 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 ips_sensor_delete? +

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

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

ips_sensor_delete is provided by the FortiOS 7 6 X MCP Server MCP server (paoloamato2/fortinet-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every FortiOS 7 6 X MCP Server tool call.

Start from FortiOS 7 6 X MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

240 FortiOS 7 6 X MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.