mikrotik_run_scheduled_task · MikroTik Cursor MCP

WHAT IT DOES

What mikrotik_run_scheduled_task does on MikroTik Cursor MCP

AI agents invoke mikrotik_run_scheduled_task 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_run_scheduled_task needs a policy

This tool triggers execution of pre-defined but opaque scheduled tasks on a MikroTik router. The actual side effects (network reconfiguration, traffic manipulation, system restart, etc.) depend entirely on what the task contains, making it an Execute risk.

From the tool's definition Tool 'manually runs a scheduled task immediately' — executes arbitrary operations (unknown scheduled task contents) on network infrastructure with effects depending on what the task contains; cannot predict outcome without knowing task payload.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mikrotik_run_scheduled_task Rate-limited

mikrotik_run_scheduled_task 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_run_scheduled_task": {
      "limits": [
        {
          "counter": "mikrotik_run_scheduled_task_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_run_scheduled_task

What does the mikrotik_run_scheduled_task tool do? +

Manually runs a scheduled task immediately. 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_run_scheduled_task? +

Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_run_scheduled_task: 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_run_scheduled_task? +

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

Can I rate-limit mikrotik_run_scheduled_task? +

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

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

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