remove_downtime
AI agents call remove_downtime to permanently remove resources in Linuxfabrik MCP Server for Icinga — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a downtime in Icinga is an irreversible deletion of a scheduled downtime entry. Once removed, alerts and notifications that were suppressed will resume, and the downtime record is gone. This cannot be undone, placing it in the Destructive category. Confidence is reduced because the description is empty and we rely solely on the tool name.
From the tool's definition Tool name: remove_downtime — description is empty, so classification is based on name alone.
Attacks that exploit this kind of access
remove_downtime. It is categorised as a Destructive tool in the Linuxfabrik MCP Server for Icinga MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Linuxfabrik MCP Server for Icinga MCP server in PolicyLayer and add a rule for remove_downtime: 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 Linuxfabrik MCP Server for Icinga. Nothing to install.
remove_downtime 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 remove_downtime 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 remove_downtime. 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.
remove_downtime is provided by the Linuxfabrik MCP Server for Icinga MCP server (linuxfabrik/mcp-server-icinga). 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 →