reschedule_check · Linuxfabrik MCP Server for Icinga MCP

WHAT IT DOES

What reschedule_check does on Linuxfabrik MCP Server for Icinga

AI agents invoke reschedule_check to trigger actions in Linuxfabrik MCP Server for Icinga. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why reschedule_check needs a policy

Rescheduling a check in Icinga triggers an external monitoring action — it causes Icinga to re-run a service or host check outside its normal schedule. This is an Execute-category action as it triggers an external operation. The description is empty, so confidence is moderate.

From the tool's definition Tool name 'reschedule_check' suggests triggering an external operation (rescheduling a monitoring check in Icinga). The server description mentions operating Icinga installations through REST APIs.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reschedule_check Rate-limited

reschedule_check stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reschedule_check": {
      "limits": [
        {
          "counter": "reschedule_check_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Linuxfabrik MCP Server for Icinga, so you can run agents against it safely.

FAQ

Questions about reschedule_check

What does the reschedule_check tool do? +

reschedule_check. It is categorised as a Execute tool in the Linuxfabrik MCP Server for Icinga MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reschedule_check? +

Register the Linuxfabrik MCP Server for Icinga MCP server in PolicyLayer and add a rule for reschedule_check: 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.

What risk level is reschedule_check? +

reschedule_check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit reschedule_check? +

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

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

reschedule_check 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.