mikrotik_create_container · MikroTik Cursor MCP

WHAT IT DOES

What mikrotik_create_container does on MikroTik Cursor MCP

AI agents invoke mikrotik_create_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_create_container needs a policy

Creating and running a container on a network device (MikroTik router) is an Execute-level action: it spins up a new execution environment that can run arbitrary code/services. Misuse could introduce malicious workloads onto a core network device, giving it high severity. It is not purely Write because the container actively executes, and not Destructive as creation is reversible.

From the tool's definition Creates a container — containers on MikroTik RouterOS run isolated execution environments, which constitutes launching an executable process/workload on the router.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mikrotik_create_container Rate-limited

mikrotik_create_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_create_container": {
      "limits": [
        {
          "counter": "mikrotik_create_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_create_container

What does the mikrotik_create_container tool do? +

Creates 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_create_container? +

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

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

Can I rate-limit mikrotik_create_container? +

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

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

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