mikrotik_start_container · MikroTik Cursor MCP

WHAT IT DOES

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 IT NEEDS A POLICY

Why mikrotik_start_container needs a policy

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…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mikrotik_start_container Rate-limited

mikrotik_start_container 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_start_container": {
      "limits": [
        {
          "counter": "mikrotik_start_container_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_start_container

What does the mikrotik_start_container tool do? +

Starts a container. 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_start_container? +

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

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

Can I rate-limit mikrotik_start_container? +

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

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

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