delete_threshold_countermeasure
Delete a countermeasure from an agent resource threshold.
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-threshold-countermeasure.md
What delete_threshold_countermeasure does on Unofficial FortiMonitor MCP Server
AI agents call delete_threshold_countermeasure 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_threshold_countermeasure is rated Critical
The tool performs an irreversible deletion of a threshold countermeasure, which cannot be undone without manual recreation. While not directly causing financial or cascading system damage, removing monitoring countermeasures could disable critical alerting mechanisms, potentially causing blind spots in infrastructure monitoring.
From the tool's definition Tool name contains 'delete' and description states 'Delete a countermeasure from an agent resource threshold' — this is an irreversible deletion operation that removes monitoring countermeasures.
Attacks that exploit this kind of access
The rule that runs delete_threshold_countermeasure safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unofficial FortiMonitor MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_threshold_countermeasure, this is the rule to start with:
delete_threshold_countermeasure is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Unofficial FortiMonitor MCP Server, apply this rule, and every delete_threshold_countermeasure call is checked against it from then on.
Questions about delete_threshold_countermeasure
Delete a countermeasure from an agent resource threshold. 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.
Register the Unofficial FortiMonitor MCP Server MCP server in PolicyLayer and add a rule for delete_threshold_countermeasure: 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.
delete_threshold_countermeasure 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_threshold_countermeasure 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_threshold_countermeasure. 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_threshold_countermeasure 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.
Across the catalogue