mikrotik_start_container

What mikrotik_start_container does on MikroTik Cursor MCP

AI agents invoke mikrotik_start_container 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 mikrotik_start_container is rated High

This tool executes a containerization operation on a MikroTik router. While not immediately destructive, starting containers can have significant side effects: network disruptions, resource exhaustion, service unavailability, or exposure of vulnerable services. An AI agent given a container name or identifier could start unintended or malicious containers.

From the tool's definition Tool name: 'mikrotik_start_container' – description: 'Starts a container'. Starting a container triggers external operations (container initialization, network binding, resource allocation) whose effects depend on which container is specified and its…

The rule that runs mikrotik_start_container safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MikroTik Cursor MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mikrotik_start_container, this is the rule to start with:

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

Questions about mikrotik_start_container