schedule_downtime
AI agents use schedule_downtime to create or update resources in Linuxfabrik MCP Server for Icinga — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linuxfabrik MCP Server for Icinga environment.
Scheduling a downtime in Icinga creates a new downtime entry that suppresses alerts for a host/service during a specified window. This is a reversible write operation (downtimes can be cancelled/deleted). The name clearly implies creating/scheduling a record rather than destroying data or executing arbitrary code. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'schedule_downtime' — description is empty and uninformative.
Attacks that exploit this kind of access
schedule_downtime. It is categorised as a Write tool in the Linuxfabrik MCP Server for Icinga MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Linuxfabrik MCP Server for Icinga MCP server in PolicyLayer and add a rule for schedule_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.
schedule_downtime is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the schedule_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 schedule_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.
schedule_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 →