mikrotik_enable_watchdog · MikroTik Cursor MCP

WHAT IT DOES

What mikrotik_enable_watchdog does on MikroTik Cursor MCP

AI agents invoke mikrotik_enable_watchdog to trigger actions in MikroTik Cursor MCP. 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 mikrotik_enable_watchdog needs a policy

Enabling a watchdog is an active system configuration change that triggers external operations (automatic reboots) depending on configuration. It's not merely writing data — it activates a hardware/software mechanism that can cause router restarts, impacting network availability. This falls under Execute due to its operational side-effects.

From the tool's definition 'Enables and configures the watchdog' — activates a system watchdog, which triggers automatic router reboots on detected failures, affecting router availability and operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mikrotik_enable_watchdog Rate-limited

mikrotik_enable_watchdog 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": {
    "mikrotik_enable_watchdog": {
      "limits": [
        {
          "counter": "mikrotik_enable_watchdog_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 MikroTik Cursor MCP, so you can run agents against it safely.

FAQ

Questions about mikrotik_enable_watchdog

What does the mikrotik_enable_watchdog tool do? +

Enables and configures the watchdog. It is categorised as a Execute tool in the MikroTik Cursor MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mikrotik_enable_watchdog? +

Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_enable_watchdog: 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 MikroTik Cursor MCP. Nothing to install.

What risk level is mikrotik_enable_watchdog? +

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

Can I rate-limit mikrotik_enable_watchdog? +

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

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

mikrotik_enable_watchdog is provided by the MikroTik Cursor MCP server (kevinpez/mikrotik-cursor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.