mikrotik_create_container_mount

What mikrotik_create_container_mount does on MikroTik Cursor MCP

AI agents use mikrotik_create_container_mount 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 mikrotik_create_container_mount is rated Medium

This tool creates/adds a new container mount point, which is a write operation that modifies system state. While not destructive (mount points can be unmounted), it could have significant impact on router container functionality and storage management. It ranks below Destructive/Execute in severity but above simple data creation due to the infrastructure-critical nature of container management on a router.

From the tool's definition Tool name 'mikrotik_create_container_mount' and description 'Creates container mount point' indicate a write operation that modifies container configuration. The action is reversible (mount points can be removed), but affects critical infrastructure.

The rule that runs mikrotik_create_container_mount 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_create_container_mount, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mikrotik_create_container_mount": {
      "limits": [
        {
          "counter": "mikrotik_create_container_mount_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about mikrotik_create_container_mount