mikrotik_enable_scheduled_task · MikroTik Cursor MCP

WHAT IT DOES

What mikrotik_enable_scheduled_task does on MikroTik Cursor MCP

AI agents use mikrotik_enable_scheduled_task to create or update resources in MikroTik Cursor MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MikroTik Cursor MCP environment.

WHY IT NEEDS A POLICY

Why mikrotik_enable_scheduled_task needs a policy

Enabling a scheduled task modifies the state of an existing task from disabled to enabled, which is a reversible configuration change (Write). However, the severity is high because enabling a scheduled task on a router can trigger arbitrary RouterOS commands to execute on a schedule, potentially causing significant network disruption, configuration changes, or other downstream effects depending on what the task does.

From the tool's definition Enables a scheduled task

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mikrotik_enable_scheduled_task Rate-limited

mikrotik_enable_scheduled_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_scheduled_task": {
      "limits": [
        {
          "counter": "mikrotik_enable_scheduled_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_scheduled_task

What does the mikrotik_enable_scheduled_task tool do? +

Enables a scheduled task. It is categorised as a Write tool in the MikroTik Cursor MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mikrotik_enable_scheduled_task? +

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

mikrotik_enable_scheduled_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mikrotik_enable_scheduled_task? +

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

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

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