mikrotik_enable_interface · MikroTik Cursor MCP

WHAT IT DOES

What mikrotik_enable_interface does on MikroTik Cursor MCP

AI agents invoke mikrotik_enable_interface 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_interface needs a policy

Enabling a network interface triggers an external operational change on a live router, affecting network topology and traffic flow. This is not a simple data write but an execution of a state-change command on network infrastructure. Misuse could re-activate unintended network paths, expose previously isolated segments, or disrupt security policies. Severity is high due to potential network-wide impact.

From the tool's definition 'Enables a network interface' — activates a previously disabled network interface on a MikroTik router via RouterOS API or SSH

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mikrotik_enable_interface Rate-limited

mikrotik_enable_interface 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_interface": {
      "limits": [
        {
          "counter": "mikrotik_enable_interface_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_interface

What does the mikrotik_enable_interface tool do? +

Enables a network interface. 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_interface? +

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

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

Can I rate-limit mikrotik_enable_interface? +

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

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

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